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

AS26669 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS26669"
JSON Docs

Warning: AS26669 (HEADLAND-COMMUNICATIONS) announces 5 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS26669
HolderHEADLAND-COMMUNICATIONS - Headland Communications
AllocationARIN, United States (US), assigned 2011-02-14
Prefixes (IPv4 / IPv6)5 / 0
RPKI valid0% (0 / 5)
Upstreams and peers1

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    5 of 5 announced prefixes have no ROA (RPKI not found): 66.167.164.0/24, 69.3.131.0/24, 209.118.211.0/24, 209.119.98.0/24, 216.5.183.0/24.

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS26669 and a max length equal to the prefix length:

    66.167.164.0/24 AS26669 max-length /24
69.3.131.0/24 AS26669 max-length /24
209.118.211.0/24 AS26669 max-length /24
209.119.98.0/24 AS26669 max-length /24
216.5.183.0/24 AS26669 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS26669 announces 5 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 5 of 5 announced prefixes have no ROA (RPKI not found): 66.167.164.0/24, 69.3.131.0/24, 209.118.211.0/24, 209.119.98.0/24, 216.5.183.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS400043): an outage there takes the whole network off the internet.
HolderHEADLAND-COMMUNICATIONS - Headland Communications
IPv4 prefixes5
IPv6 prefixes0
RPKI5 not found
Downstream networks0
Routes to fix
PrefixRPKI
66.167.164.0/24 No ROA
69.3.131.0/24 No ROA
209.118.211.0/24 No ROA
209.119.98.0/24 No ROA
216.5.183.0/24 No ROA

Upstreams and peers seen to the left 1

AS400043 IBRIDGE-01

Announced prefixes 5

66.167.164.0/24 69.3.131.0/24 209.118.211.0/24 209.119.98.0/24 216.5.183.0/24

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameHEADLAND-COMMUNICATIONS
HandleAS26669
RangeAS26669
Statusactive
Registered2011-02-14T14:05:11-05:00
Last changed2012-02-24T09:44:34-05:00
Abuse contactJAMUEL@my740il.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2011-02-14
StatusAssigned
Delegated rangeAS26669

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

Contacts
RoleNameEmail
registrant Headland Communications
noc, abuse, technical JAMUEL PHILLIP STARKEY JAMUEL@my740il.com

Source: https://rdap.arin.net/registry/autnum/26669. 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

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup