Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
187.76.192.0/18 ·
Warning: 187.76.192.0/18 is announced by AS7738 (AS7738). 1 warning
| Announced as | 187.76.192.0/18 |
|---|---|
| Origin AS | AS7738 AS7738 |
| Holder | V tal |
| Allocation | LACNIC, Brazil (BR), allocated 2009-07-01 |
| Size | 16,384 addresses |
| Abuse contact | abuse@vtal.com |
What to fix
-
Warning
187.76.192.0/18 from AS7738 is RPKI not found: no ROA covers it.
Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.
Fix: Create a ROA for this prefix with origin AS7738 and a max length equal to the prefix length.
prefix: 187.76.192.0/18 origin: AS7738 max-length: 18
Checks
Routing and RPKI 187.76.192.0/18 from AS7738 is RPKI not found: no ROA covers it.
- Pass: Announced as 187.76.192.0/18 by AS7738.
- Warning: 187.76.192.0/18 from AS7738 is RPKI not found: no ROA covers it.
- Pass: Seen by 99% of RIPE RIS peers.
| Route | 187.76.192.0/18 |
|---|---|
| Origin AS | AS7738 AS7738 - V tal No ROA |
| IRR route objects | RADB |
| Visibility (RIS peers) | 319 / 321 |
| First seen | 2017-02-21 |
| Covering prefixes | 187.76.0.0/16 |
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is delegated for all 10 zones checked.
- Pass: Reverse DNS is delegated for all 10 zones checked.
- Info: Only the first 10 of 64 reverse zones were checked.
| Zone | Nameservers |
|---|---|
| 192.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
| 193.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
| 194.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
| 195.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
| 196.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br, ns9.telemar.net.br |
| 197.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
| 198.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
| 199.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
| 200.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
| 201.76.187.in-addr.arpa | ns2.telemar.net.br, ns4.telemar.net.br |
Registration Found at rdap.lacnic.net.
- Pass: Found at rdap.lacnic.net.
| Name | 514650 |
|---|---|
| Handle | 187.76.0.0/16 |
| Range | 187.76.0.0 – 187.76.255.255 |
| Country | BR |
| Status | active |
| Registered | 2009-07-01T15:00:43Z |
| Last changed | 2025-05-12T14:23:10Z |
| Abuse contact | abuse@vtal.com |
| Registry (RIR) | LACNIC |
|---|---|
| Country | Brazil (BR) |
| Delegated on | 2009-07-01 |
| Status | Allocated |
| Delegated range | 187.76.0.0/16 (187.76.0.0 – 187.76.255.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | V tal | |
| technical | Centro de Gerencia de Rede TELEMAR | ld-numeracaoip@vtal.com |
| abuse | Segurança da Informação Vtal | abuse@vtal.com |
Source: https://rdap.lacnic.net/rdap/ip/187.76.192.0/18. Registration data from rdap.lacnic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS7738 is in PeeringDB as Vtal 7738.
- Info: Peering policy: Open.
- Info: No internet exchange ports are listed.
- Warning: No public NOC, policy or technical contact.
About the network that announces this space, so not in the fix list.
| Network | Vtal 7738 (Telemar/Pegasus/Oi/Vtal) |
|---|---|
| AS number | AS7738 |
| Type | NSP, Global |
| Website | http://www.vtal.com |
| IRR as-set | RADB::AS-OINETBR |
| Prefixes (IPv4 / IPv6) | 30000 / 10000 |
| Traffic | Mostly Inbound |
| Peering policy | Open |
| Locations | Required - US |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-11-02 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup