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

AS34178 · 

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

Warning: AS34178 (Qinetiq Qinetiq Limited) announces 4 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS34178
HolderQinetiq Qinetiq Limited
AllocationRIPE NCC, United Kingdom (GB), allocated 2004-11-12
Prefixes (IPv4 / IPv6)4 / 0
RPKI valid0% (0 / 4)
Upstreams and peers2

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

    4 of 4 announced prefixes have no ROA (RPKI not found): 185.76.92.0/24, 185.76.95.0/24, 192.102.214.0/24, 192.150.204.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 AS34178 and a max length equal to the prefix length:

    185.76.92.0/24 AS34178 max-length /24
185.76.95.0/24 AS34178 max-length /24
192.102.214.0/24 AS34178 max-length /24
192.150.204.0/24 AS34178 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    1 of 4 announced prefixes have no IRR route object: 185.76.95.0/24.

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

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS34178 in your RIR’s IRR database (or RADB).

    route: 185.76.95.0/24
origin: AS34178

    Open in ASN & BGP prefix lookup

  4. 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: AS34178 announces 4 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 185.76.92.0/24, 185.76.95.0/24, 192.102.214.0/24, 192.150.204.0/24.
  • Warning: 1 of 4 announced prefixes have no IRR route object: 185.76.95.0/24.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderQinetiq Qinetiq Limited
IPv4 prefixes4
IPv6 prefixes0
RPKI4 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
185.76.92.0/24 No ROA
185.76.95.0/24 No ROA
192.102.214.0/24 No ROA
192.150.204.0/24 No ROA

Upstreams and peers seen to the left 2

AS3257 GTT AS286 GTT

Announced prefixes 4

185.76.92.0/24 185.76.95.0/24 192.102.214.0/24 192.150.204.0/24

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameQinetiq
HandleAS34178
RangeAS34178
Statusactive
Registered2004-11-12T11:19:36Z
Last changed2023-06-23T06:56:50Z
Abuse contactnetsecurity@qinetiq.com
Allocation
Registry (RIR)RIPE NCC
CountryUnited Kingdom (GB)
Delegated on2004-11-12
StatusAllocated
Delegated rangeAS34178

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

Contacts
RoleNameEmail
registrant Qinetiq Limited
registrant QINETIQ-FRN-UK-MNT
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role netsecurity@qinetiq.com

Source: https://rdap.db.ripe.net/autnum/34178. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

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