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

AS41206 ·

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

Warning: AS41206 (United-Telecom-HU-AS United Telecom Zar…) announces 3 IPv4 and 1 IPv6 prefixes. 2 warnings

AS pageAS41206
HolderUnited-Telecom-HU-AS United Telecom Zartkoruen Mukodo Reszvenytarsasag
AllocationRIPE NCC, Hungary (HU), allocated 2017-08-28
Prefixes (IPv4 / IPv6)3 / 1
RPKI valid0% (0 / 4)
Upstreams and peers11
Peering policyOpen

What to fix

  1. Warning

    4 of 4 announced prefixes have no ROA (RPKI not found): 185.219.48.0/22, 185.219.48.0/23, 185.219.50.0/23, 2a0b:e0c0::/29.

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

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

    185.219.48.0/22 AS41206 max-length /22
    185.219.48.0/23 AS41206 max-length /23
    185.219.50.0/23 AS41206 max-length /23
    2a0b:e0c0::/29 AS41206 max-length /29

    Open in RPKI / ROA validator Guide

  2. 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 4 of 4 announced prefixes have no ROA (RPKI not found): 185.219.48.0/22, 185.219.48.0/23, 185.219.50.0/23, 2a0b:e0c0::/29.
  • Pass: AS41206 announces 3 IPv4 and 1 IPv6 prefixes.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 185.219.48.0/22, 185.219.48.0/23, 185.219.50.0/23, 2a0b:e0c0::/29.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 11 upstreams and peers, 11 downstream networks seen.
HolderUnited-Telecom-HU-AS United Telecom Zartkoruen Mukodo Reszvenytarsasag
IPv4 prefixes3
IPv6 prefixes1
RPKI4 not found
Downstream networks11
Routes to fix
PrefixRPKI
185.219.48.0/22 No ROA
185.219.48.0/23 No ROA
185.219.50.0/23 No ROA
2a0b:e0c0::/29 No ROA

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.
NameUnited-Telecom-HU-AS
HandleAS41206
RangeAS41206
Statusactive
Registered2017-08-28T16:52:50Z
Last changed2026-05-27T10:13:00Z
Abuse contactabuse@unitedtelecom.hu
Allocation
Registry (RIR)RIPE NCC
CountryHungary (HU)
Delegated on2017-08-28
StatusAllocated
Delegated rangeAS41206

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

Contacts
RoleNameEmail
registrant hu-unitedtelecom-1-mnt
registrant United Telecom Zartkoruen Mukodo Reszvenytarsasag
registrant RIPE-NCC-END-MNT
abuse United Telecom abuse abuse@unitedtelecom.hu

Source: https://rdap.db.ripe.net/autnum/41206. 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 public NOC, policy or technical contact.
  • Pass: AS41206 is in PeeringDB as United Telecom Zrt..
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 2 ports (20G in total).
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkUnited Telecom Zrt. (United Telecom)
AS numberAS41206
Type, Not Disclosed
Websitehttps://unitedtelecom.hu
IRR as-setRIPE::AS-UNITEDTELECOM
Prefixes (IPv4 / IPv6)300 / 30
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup