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

91.103.9.0/24 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=91.103.9.0%2F24"
JSON Docs

Warning: 91.103.9.0/24 is announced by AS3758 (SINGNET). 3 warnings

Announced as91.103.9.0/24
Origin ASAS3758 SINGNET
Holderde-khsgmbh-1-mnt
AllocationRIPE NCC, Germany (DE), allocated 2018-06-22
Size256 addresses
Abuse contactabuse@khs.com

What to fix

  1. Warning

    91.103.9.0/24 from AS3758 is RPKI not found: no ROA covers it.

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS3758 and a max length equal to the prefix length.

    prefix: 91.103.9.0/24
    origin: AS3758
    max-length: 24

    Open in RPKI / ROA validator Guide

  2. Warning

    No IRR route object for 91.103.9.0/24 with origin AS3758.

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

    Fix: Create a route object in your RIR’s IRR database (or RADB):

    route: 91.103.9.0/24
    origin: AS3758

    Open in ASN & BGP prefix lookup

  3. Warning

    Reverse DNS is not delegated for 91.103.9.0/24, so its addresses have no PTR records.

    Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.

    Fix: Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.

    Open in DNS lookup

Checks

Routing and RPKI 91.103.9.0/24 from AS3758 is RPKI not found: no ROA covers it.
  • Pass: Announced as 91.103.9.0/24 by AS3758.
  • Warning: 91.103.9.0/24 from AS3758 is RPKI not found: no ROA covers it.
  • Warning: No IRR route object for 91.103.9.0/24 with origin AS3758.
  • Pass: Seen by 100% of RIPE RIS peers.
Route91.103.9.0/24
Origin ASAS3758 SINGNET - SingNet No ROA
Visibility (RIS peers)320 / 320
First seen2007-03-28

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 91.103.9.0/24, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 91.103.9.0/24, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
9.103.91.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameKHS-SG
Handle91.103.9.0 - 91.103.9.255
Range91.103.9.0 – 91.103.9.255
CountrySG
Statusactive
Registered2020-11-11T15:55:04Z
Last changed2021-01-21T10:32:27Z
Abuse contactabuse@khs.com
Allocation
Registry (RIR)RIPE NCC
CountryGermany (DE)
Delegated on2018-06-22
StatusAllocated
Delegated range91.103.8.0/22 (91.103.8.0 – 91.103.11.255)

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

Contacts
RoleNameEmail
registrant de-khsgmbh-1-mnt
abuse Abuse-C Role abuse@khs.com

Source: https://rdap.db.ripe.net/ip/91.103.9.0/24. 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: AS3758 is in PeeringDB as SingNet.
  • 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 2022-07-27.

About the network that announces this space, so not in the fix list.

NetworkSingNet
AS numberAS3758
Type, Not Disclosed
Prefixes (IPv4 / IPv6)0 / 0
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