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

AS28924 ·

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

Warning: AS28924 (INTEGRITY-HU-AS) announces 12 IPv4 and 12 IPv6 prefixes. 3 warnings

AS pageAS28924
HolderINTEGRITY-HU-AS INTEGRITY Informatics Ltd.
AllocationRIPE NCC, Hungary (HU), allocated 2003-04-08
Prefixes (IPv4 / IPv6)12 / 12
RPKI valid92% (22 / 24)
Upstreams and peers2

What to fix

  1. Warning

    2 of 24 announced prefixes have no ROA (RPKI not found): 91.220.29.0/24, 2a01:7d80:2000::/36.

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

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

    91.220.29.0/24 AS28924 max-length /24
    2a01:7d80:2000::/36 AS28924 max-length /36

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  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 2 of 24 announced prefixes have no ROA (RPKI not found): 91.220.29.0/24, 2a01:7d80:2000::/36.
  • Pass: AS28924 announces 12 IPv4 and 12 IPv6 prefixes.
  • Warning: 2 of 24 announced prefixes have no ROA (RPKI not found): 91.220.29.0/24, 2a01:7d80:2000::/36.
  • Info: 22 of 24 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 2 downstream networks seen.
HolderINTEGRITY-HU-AS INTEGRITY Informatics Ltd.
IPv4 prefixes12
IPv6 prefixes12
RPKI22 valid · 2 not found
Downstream networks2
Routes to fix
PrefixRPKI
91.220.29.0/24 No ROA
2a01:7d80:2000::/36 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.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameINTEGRITY-HU-AS
HandleAS28924
RangeAS28924
Statusactive
Registered2003-04-08T08:22:29Z
Last changed2025-05-22T19:21:55Z
Abuse contactnoc@integrity.hu
Allocation
Registry (RIR)RIPE NCC
CountryHungary (HU)
Delegated on2003-04-08
StatusAllocated
Delegated rangeAS28924

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

Contacts
RoleNameEmail
registrant INTEGRITY-HU-MNT
registrant INTEGRITY Informatics Ltd.
registrant QWERTY-MNT
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role noc@integrity.hu

Source: https://rdap.db.ripe.net/autnum/28924. 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 No IRR as-set is listed.
  • Pass: AS28924 is in PeeringDB as INTEGRITY Informatics.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2023-03-29.
NetworkINTEGRITY Informatics
AS numberAS28924
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Ratio requiredNo
Last updated2023-03-29

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup