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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
45.131.100.0/22 ·
Warning: 45.131.100.0/22 is announced by AS43513 (NANO-AS Sia Nano IT). 2 warnings
| Announced as | 45.131.100.0/22 |
|---|---|
| Origin AS | AS43513 NANO-AS Sia Nano IT |
| Holder | in-hostroyale-1-mnt |
| Allocation | RIPE NCC, India (IN), allocated 2019-07-19 |
| Size | 1,024 addresses |
| Abuse contact | abuse@hostroyale.com |
What to fix
-
Warning
45.131.100.0/22 from AS43513 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 AS43513 and a max length equal to the prefix length.
prefix: 45.131.100.0/22 origin: AS43513 max-length: 22
-
Warning
Reverse DNS is not delegated for 45.131.100.0/22, 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.
Checks
Routing and RPKI 45.131.100.0/22 from AS43513 is RPKI not found: no ROA covers it.
- Pass: Announced as 45.131.100.0/22 by AS43513.
- Warning: 45.131.100.0/22 from AS43513 is RPKI not found: no ROA covers it.
- Pass: Seen by 99% of RIPE RIS peers.
| Route | 45.131.100.0/22 |
|---|---|
| Origin AS | AS43513 NANO-AS Sia Nano IT No ROA |
| IRR route objects | RIPE |
| Visibility (RIS peers) | 315 / 317 |
| First seen | 2019-10-14 |
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is not delegated for 45.131.100.0/22, so its addresses have no PTR records.
- Warning: Reverse DNS is not delegated for 45.131.100.0/22, so its addresses have no PTR records.
| Zone | Nameservers |
|---|---|
| 100.131.45.in-addr.arpa | Not delegated |
| 101.131.45.in-addr.arpa | Not delegated |
| 102.131.45.in-addr.arpa | Not delegated |
| 103.131.45.in-addr.arpa | Not delegated |
Registration Found at rdap.arin.net.
- Pass: Found at rdap.arin.net.
| Name | IN-HOSTROYALE-20190719 |
|---|---|
| Handle | 45.131.100.0 - 45.131.103.255 |
| Range | 45.131.100.0 – 45.131.103.255 |
| Country | LV |
| Status | active |
| Registered | 2022-09-21T14:07:46Z |
| Last changed | 2023-05-15T10:04:26Z |
| Abuse contact | abuse@hostroyale.com |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | India (IN) |
| Delegated on | 2019-07-19 |
| Status | Allocated |
| Delegated range | 45.131.100.0/22 (45.131.100.0 – 45.131.103.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | in-hostroyale-1-mnt | |
| registrant | HostRoyale Technologies Pvt Ltd | |
| registrant | RIPE-NCC-HM-MNT | |
| administrative, technical | NOC Admin | |
| abuse | Abuse-C Role | abuse@hostroyale.com |
Source: https://rdap.arin.net/registry/ip/45.131.100.0/22. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS43513 is in PeeringDB as Nano IT.
- Info: Peering policy: Open.
- Info: Present at 1 internet exchanges with 1 ports (10G in total).
- Warning: No public NOC, policy or technical contact.
About the network that announces this space, so not in the fix list.
| Network | Nano IT |
|---|---|
| AS number | AS43513 |
| Type | NSP, Europe |
| Website | http://www.nano.lv |
| IRR as-set | AS-NANOIT |
| Prefixes (IPv4 / IPv6) | 400 / 50 |
| Traffic | 20-50Gbps, Mostly Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2025-10-01 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup