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

AS54037 ·

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

Warning: AS54037 (DCA-LN) announces 5 IPv4 and 0 IPv6 prefixes. 3 warnings

AS pageAS54037
HolderDCA-LN - DCA LLC
AllocationARIN, United States (US), assigned 2018-10-29
Prefixes (IPv4 / IPv6)5 / 0
RPKI valid0% (0 / 5)
Upstreams and peers2
Peering policySelective

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): 141.193.220.0/23, 141.193.221.0/24, 162.213.68.0/23, 162.213.68.0/24, 162.213.69.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 AS54037 and a max length equal to the prefix length:

    141.193.220.0/23 AS54037 max-length /23
    141.193.221.0/24 AS54037 max-length /24
    162.213.68.0/23 AS54037 max-length /23
    162.213.68.0/24 AS54037 max-length /24
    162.213.69.0/24 AS54037 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS54037 announces 5 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 5 of 5 announced prefixes have no ROA (RPKI not found): 141.193.220.0/23, 141.193.221.0/24, 162.213.68.0/23, 162.213.68.0/24, 162.213.69.0/24.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 1 downstream networks seen.
HolderDCA-LN - DCA LLC
IPv4 prefixes5
IPv6 prefixes0
RPKI5 not found
Downstream networks1
Routes to fix
PrefixRPKI
141.193.220.0/23 No ROA
141.193.221.0/24 No ROA
162.213.68.0/23 No ROA
162.213.68.0/24 No ROA
162.213.69.0/24 No ROA

Upstreams and peers seen to the left 2

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.
NameDCA-LN
HandleAS54037
RangeAS54037
Statusactive
Registered2018-10-29T13:58:57-04:00
Last changed2018-10-29T13:58:57-04:00
Abuse contactnoc@dcaonline.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2018-10-29
StatusAssigned
Delegated rangeAS54037

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

Contacts
RoleNameEmail
registrant DCA LLC

Source: https://rdap.arin.net/registry/autnum/54037. 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 No public NOC, policy or technical contact.
  • Pass: AS54037 is in PeeringDB as Lockridge Networks.
  • Info: Peering policy: Selective.
  • Info: Present at 3 internet exchanges with 3 ports (21G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkLockridge Networks
AS numberAS54037
TypeEnterprise, North America
Websitehttp://www.lockridge.net
IRR as-setAS-DCA-LN
Prefixes (IPv4 / IPv6)4 / 0
Traffic5-10Gbps, Mostly Inbound
Peering policySelective
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2025-05-23
Contacts
Abuseabuse@lockridge.net
Salessales@lockridge.net

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup