Skip to content
thenetworkery

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.

IP address, prefix or AS number

187.76.0.0/16 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=187.76.0.0%2F16"
JSON Docs

Warning: 187.76.0.0/16 is announced by AS7738 (AS7738). 6 warnings

Announced as187.76.0.0/16
Origin ASAS7738 AS7738
HolderV tal
AllocationLACNIC, Brazil (BR), allocated 2009-07-01
Size65,536 addresses
Abuse contactabuse@vtal.com

What to fix

  1. Warning

    187.76.0.0/16 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.0.0/16
    origin: AS7738
    max-length: 16

    Open in RPKI / ROA validator Guide

  2. Warning

    187.76.0.0/18 from AS7738 is RPKI not found: no ROA covers it. 187.76.0.0/18

    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.0.0/18
    origin: AS7738
    max-length: 18

    Open in RPKI / ROA validator Guide

  3. Warning

    187.76.64.0/18 from AS7738 is RPKI not found: no ROA covers it. 187.76.64.0/18

    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.64.0/18
    origin: AS7738
    max-length: 18

    Open in RPKI / ROA validator Guide

  4. Warning

    187.76.128.0/18 from AS7738 is RPKI not found: no ROA covers it. 187.76.128.0/18

    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.128.0/18
    origin: AS7738
    max-length: 18

    Open in RPKI / ROA validator Guide

  5. Warning

    187.76.192.0/18 from AS7738 is RPKI not found: no ROA covers it. 187.76.192.0/18

    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

    Open in RPKI / ROA validator Guide

  6. Warning

    Reverse DNS is not delegated for 187.76.0.0/16, so its addresses have no PTR records.

    Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.

    Fix: Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.

    Open in DNS lookup

Checks

Routing and RPKI 187.76.0.0/16 from AS7738 is RPKI not found: no ROA covers it.
  • Pass: Announced as 187.76.0.0/16 by AS7738.
  • Warning: 187.76.0.0/16 from AS7738 is RPKI not found: no ROA covers it.
  • Warning: 187.76.0.0/18 from AS7738 is RPKI not found: no ROA covers it. 187.76.0.0/18
  • Warning: 187.76.64.0/18 from AS7738 is RPKI not found: no ROA covers it. 187.76.64.0/18
  • Warning: 187.76.128.0/18 from AS7738 is RPKI not found: no ROA covers it. 187.76.128.0/18
  • Warning: 187.76.192.0/18 from AS7738 is RPKI not found: no ROA covers it. 187.76.192.0/18
  • Pass: Seen by 100% of RIPE RIS peers.
Route187.76.0.0/16
Origin ASAS7738 AS7738 - V tal No ROA
IRR route objectsRADB
Visibility (RIS peers)318 / 319
First seen2009-07-07
More-specific routes 4
More-specific routeOrigin ASRPKI
187.76.0.0/18 AS7738 No ROA
187.76.64.0/18 AS7738 No ROA
187.76.128.0/18 AS7738 No ROA
187.76.192.0/18 AS7738 No ROA

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 187.76.0.0/16, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 187.76.0.0/16, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
76.187.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.lacnic.net.
  • Pass: Found at rdap.lacnic.net.
Name514650
Handle187.76.0.0/16
Range187.76.0.0 – 187.76.255.255
CountryBR
Statusactive
Registered2009-07-01T15:00:43Z
Last changed2025-05-12T14:23:10Z
Abuse contactabuse@vtal.com
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2009-07-01
StatusAllocated
Delegated range187.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.

Contacts
RoleNameEmail
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.0.0/16. Registration data from rdap.lacnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB 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.

NetworkVtal 7738 (Telemar/Pegasus/Oi/Vtal)
AS numberAS7738
TypeNSP, Global
Websitehttp://www.vtal.com
IRR as-setRADB::AS-OINETBR
Prefixes (IPv4 / IPv6)30000 / 10000
TrafficMostly Inbound
Peering policyOpen
LocationsRequired - US
Ratio requiredNo
ContractsNot Required
Last updated2026-11-02

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup