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

152.196.0.0/22 ·

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

Warning: 152.196.0.0/22 is announced by AS1339 (ANSBB-ASNNET-1). 4 warnings

Announced as152.196.0.0/22
Origin ASAS1339 ANSBB-ASNNET-1
HolderVerizon Business
AllocationARIN, United States (US), allocated 1992-04-01
Size1,024 addresses
Abuse contactabuse@verizon.com

What to fix

  1. Warning

    152.196.0.0/22 from AS1339 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 AS1339 and a max length equal to the prefix length.

    prefix: 152.196.0.0/22
    origin: AS1339
    max-length: 22

    Open in RPKI / ROA validator Guide

  2. Warning

    152.196.0.0/24 from AS1339 is RPKI not found: no ROA covers it. 152.196.0.0/24

    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 AS1339 and a max length equal to the prefix length.

    prefix: 152.196.0.0/24
    origin: AS1339
    max-length: 24

    Open in RPKI / ROA validator Guide

  3. Warning

    No IRR route object for 152.196.0.0/22 with origin AS1339.

    Many networks build their prefix filters from IRR data; without a route object some of them drop the route.

    Fix: Create a route object in your RIR’s IRR database (or RADB):

    route: 152.196.0.0/22
    origin: AS1339

    Open in ASN & BGP prefix lookup

  4. Warning

    Reverse DNS is not delegated for 152.196.0.0/22, 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 152.196.0.0/22 from AS1339 is RPKI not found: no ROA covers it.
  • Pass: Announced as 152.196.0.0/22 by AS1339.
  • Warning: 152.196.0.0/22 from AS1339 is RPKI not found: no ROA covers it.
  • Warning: 152.196.0.0/24 from AS1339 is RPKI not found: no ROA covers it. 152.196.0.0/24
  • Warning: No IRR route object for 152.196.0.0/22 with origin AS1339.
  • Pass: Seen by 100% of RIPE RIS peers.
Route152.196.0.0/22
Origin ASAS1339 ANSBB-ASNNET-1 - Verizon Business No ROA
Visibility (RIS peers)321 / 321
First seen2025-12-04
Covering prefixes152.192.0.0/13
More-specific routes 1
More-specific routeOrigin ASRPKI
152.196.0.0/24 AS1339 No ROA

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 152.196.0.0/22, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 152.196.0.0/22, so its addresses have no PTR records.
Reverse zones 4
ZoneNameservers
0.196.152.in-addr.arpa Not delegated
1.196.152.in-addr.arpa Not delegated
2.196.152.in-addr.arpa Not delegated
3.196.152.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameUU-152-176
HandleNET-152-176-0-0-1
Range152.176.0.0 – 152.199.255.255
Statusactive
Registered1992-04-01T00:00:00-05:00
Last changed2024-03-04T11:28:23-05:00
Abuse contactabuse@verizon.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on1992-04-01
StatusAllocated
Delegated range152.192.0.0/13 (152.192.0.0 – 152.199.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 Verizon Business

Source: https://rdap.arin.net/registry/ip/152.196.0.0/22. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

About the network that announces this space, so not in the fix list.

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup