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

AS55736 ·

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

Warning: AS55736 (DataKnox-DNX) announces 11 IPv4 and 2 IPv6 prefixes. 3 warnings

AS pageAS55736
HolderDataKnox-DNX - Dataknox Pty Limited
AllocationAPNIC, Australia (AU), allocated 2015-10-13
Prefixes (IPv4 / IPv6)11 / 2
RPKI valid69% (9 / 13)
Upstreams and peers1
Peering policyOpen

What to fix

  1. Warning

    4 of 13 announced prefixes have no ROA (RPKI not found): 103.160.130.0/24, 103.160.131.0/24, 202.157.179.0/24, 2001:df5:9780::/48.

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

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

    103.160.130.0/24 AS55736 max-length /24
    103.160.131.0/24 AS55736 max-length /24
    202.157.179.0/24 AS55736 max-length /24
    2001:df5:9780::/48 AS55736 max-length /48

    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 4 of 13 announced prefixes have no ROA (RPKI not found): 103.160.130.0/24, 103.160.131.0/24, 202.157.179.0/24, 2001:df5:9780::/48.
  • Pass: AS55736 announces 11 IPv4 and 2 IPv6 prefixes.
  • Warning: 4 of 13 announced prefixes have no ROA (RPKI not found): 103.160.130.0/24, 103.160.131.0/24, 202.157.179.0/24, 2001:df5:9780::/48.
  • Info: 9 of 13 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: One upstream or peer seen (AS136204): an outage there takes the whole network off the internet.
HolderDataKnox-DNX - Dataknox Pty Limited
IPv4 prefixes11
IPv6 prefixes2
RPKI9 valid · 4 not found
Downstream networks3
Routes to fix
PrefixRPKI
103.160.130.0/24 No ROA
103.160.131.0/24 No ROA
202.157.179.0/24 No ROA
2001:df5:9780::/48 No ROA

Upstreams and peers seen to the left 1

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameDataKnox-DNX
HandleAS55736
RangeAS55736
CountryAU
Statusactive
Registered2010-08-24T22:57:33Z
Last changed2020-07-15T13:10:25Z
Abuse contactqasim.ali@dataknox.com.au
Allocation
Registry (RIR)APNIC
CountryAustralia (AU)
Delegated on2015-10-13
StatusAllocated
Delegated rangeAS55736

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

Contacts
RoleNameEmail
registrant TRIFORCE SERVICES AUSTRALIA PTY LTD qasim@triforce.com.au
abuse IRT-TSA-AU qasim.ali@dataknox.com.au
administrative, technical Husayn Aly Husayn.Aly@dataknox.com.au

Source: https://rdap.apnic.net/autnum/55736. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS55736 is in PeeringDB as DataKnox-DNX.
  • Info: Peering policy: Open.
  • 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 2024-11-11.
NetworkDataKnox-DNX
AS numberAS55736
TypeCable/DSL/ISP, Not Disclosed
Websitehttps://www.triforce.com.au
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2024-11-11

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup