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

74.220.96.0/19 ·

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

Warning: 74.220.96.0/19 is announced by AS17307 (VIRTELA-1). 11 warnings

Announced as74.220.96.0/19
Origin ASAS17307 VIRTELA-1
HolderNTT Global Networks Incorporated
AllocationARIN, United States (US), allocated 2007-01-08
Size8,192 addresses
Abuse contactBackboneTeam@nttglobal.net

What to fix

  1. Warning

    74.220.96.0/19 from AS17307 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 AS17307 and a max length equal to the prefix length.

    prefix: 74.220.96.0/19
    origin: AS17307
    max-length: 19

    Open in RPKI / ROA validator Guide

  2. Warning

    74.220.96.0/20 from AS17307 is RPKI not found: no ROA covers it. 74.220.96.0/20

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

    prefix: 74.220.96.0/20
    origin: AS17307
    max-length: 20

    Open in RPKI / ROA validator Guide

  3. Warning

    74.220.96.0/24 from AS11158 is RPKI not found: no ROA covers it. 74.220.96.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 AS11158 and a max length equal to the prefix length.

    prefix: 74.220.96.0/24
    origin: AS11158
    max-length: 24

    Open in RPKI / ROA validator Guide

  4. Warning

    74.220.97.0/24 from AS18488 is RPKI not found: no ROA covers it. 74.220.97.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 AS18488 and a max length equal to the prefix length.

    prefix: 74.220.97.0/24
    origin: AS18488
    max-length: 24

    Open in RPKI / ROA validator Guide

  5. Warning

    74.220.98.0/24 from AS18484 is RPKI not found: no ROA covers it. 74.220.98.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 AS18484 and a max length equal to the prefix length.

    prefix: 74.220.98.0/24
    origin: AS18484
    max-length: 24

    Open in RPKI / ROA validator Guide

  6. Warning

    74.220.100.0/24 from AS18484 is RPKI not found: no ROA covers it. 74.220.100.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 AS18484 and a max length equal to the prefix length.

    prefix: 74.220.100.0/24
    origin: AS18484
    max-length: 24

    Open in RPKI / ROA validator Guide

  7. Warning

    74.220.101.0/24 from AS19808 is RPKI not found: no ROA covers it. 74.220.101.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 AS19808 and a max length equal to the prefix length.

    prefix: 74.220.101.0/24
    origin: AS19808
    max-length: 24

    Open in RPKI / ROA validator Guide

  8. Warning

    74.220.102.0/24 from AS18491 is RPKI not found: no ROA covers it. 74.220.102.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 AS18491 and a max length equal to the prefix length.

    prefix: 74.220.102.0/24
    origin: AS18491
    max-length: 24

    Open in RPKI / ROA validator Guide

  9. Warning

    74.220.103.0/24 from AS19804 is RPKI not found: no ROA covers it. 74.220.103.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 AS19804 and a max length equal to the prefix length.

    prefix: 74.220.103.0/24
    origin: AS19804
    max-length: 24

    Open in RPKI / ROA validator Guide

  10. Warning

    74.220.104.0/24 from AS18485 is RPKI not found: no ROA covers it. 74.220.104.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 AS18485 and a max length equal to the prefix length.

    prefix: 74.220.104.0/24
    origin: AS18485
    max-length: 24

    Open in RPKI / ROA validator Guide

  11. Warning

    74.220.105.0/24 from AS19809 is RPKI not found: no ROA covers it. 74.220.105.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 AS19809 and a max length equal to the prefix length.

    prefix: 74.220.105.0/24
    origin: AS19809
    max-length: 24

    Open in RPKI / ROA validator Guide

Checks

Routing and RPKI 74.220.96.0/19 from AS17307 is RPKI not found: no ROA covers it.
  • Pass: Announced as 74.220.96.0/19 by AS17307.
  • Warning: 74.220.96.0/19 from AS17307 is RPKI not found: no ROA covers it.
  • Warning: 74.220.96.0/20 from AS17307 is RPKI not found: no ROA covers it. 74.220.96.0/20
  • Warning: 74.220.96.0/24 from AS11158 is RPKI not found: no ROA covers it. 74.220.96.0/24
  • Warning: 74.220.97.0/24 from AS18488 is RPKI not found: no ROA covers it. 74.220.97.0/24
  • Warning: 74.220.98.0/24 from AS18484 is RPKI not found: no ROA covers it. 74.220.98.0/24
  • Warning: 74.220.100.0/24 from AS18484 is RPKI not found: no ROA covers it. 74.220.100.0/24
  • Warning: 74.220.101.0/24 from AS19808 is RPKI not found: no ROA covers it. 74.220.101.0/24
  • Warning: 74.220.102.0/24 from AS18491 is RPKI not found: no ROA covers it. 74.220.102.0/24
  • Warning: 74.220.103.0/24 from AS19804 is RPKI not found: no ROA covers it. 74.220.103.0/24
  • Warning: 74.220.104.0/24 from AS18485 is RPKI not found: no ROA covers it. 74.220.104.0/24
  • Warning: 74.220.105.0/24 from AS19809 is RPKI not found: no ROA covers it. 74.220.105.0/24
  • Pass: Seen by 100% of RIPE RIS peers.
Route74.220.96.0/19
Origin ASAS17307 VIRTELA-1 - NTT Global Networks Incorporated No ROA
IRR route objectsRADB, RIPE-NONAUTH
Visibility (RIS peers)320 / 320
First seen2007-10-20
More-specific routes 20
More-specific routeOrigin ASRPKI
74.220.96.0/20 AS17307 No ROA
74.220.96.0/24 AS11158 No ROA
74.220.97.0/24 AS18488 No ROA
74.220.98.0/24 AS18484 No ROA
74.220.100.0/24 AS18484 No ROA
74.220.101.0/24 AS19808 No ROA
74.220.102.0/24 AS18491 No ROA
74.220.103.0/24 AS19804 No ROA
74.220.104.0/24 AS18485 No ROA
74.220.105.0/24 AS19809 No ROA
74.220.108.0/24 AS18486
74.220.110.0/24 AS18491
74.220.112.0/24 AS19803
74.220.113.0/24 AS19804
74.220.117.0/24 AS19803
74.220.119.0/24 AS18484
74.220.120.0/24 AS18491
74.220.121.0/24 AS19804
74.220.123.0/24 AS19808
74.220.124.0/24 AS19803

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse 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 32 reverse zones were checked.
Reverse zones 32
ZoneNameservers
96.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
97.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
98.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
99.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
100.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
101.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
102.220.74.in-addr.arpa ns1.nttglobal.net, ns2.nttglobal.net, ns3.nttglobal.net
103.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
104.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
105.220.74.in-addr.arpa dcoeng1-tdnsp-4.nttgn_public, dcoeng1-tdnspm-1.nttgn_public, dtxdal2-tdnsp-3.nttgn_public
Open in DNS lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameVRTL-NET-6
HandleNET-74-220-96-0-1
Range74.220.96.0 – 74.220.127.255
Statusactive
Registered2007-01-08T11:51:00-05:00
Last changed2012-03-02T08:03:18-05:00
Abuse contactBackboneTeam@nttglobal.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2007-01-08
StatusAllocated
Delegated range74.220.96.0/19 (74.220.96.0 – 74.220.127.255)

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant NTT Global Networks Incorporated
abuse, noc, technical Virtela Global Operations Center BackboneTeam@nttglobal.net

Source: https://rdap.arin.net/registry/ip/74.220.96.0/19. 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