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.
167.179.207.0/24 ·
Warning: 167.179.207.0/24 is announced by AS45474 (NEXUSGUARD-AS-AP). 1 warning
| Announced as | 167.179.207.0/24 |
|---|---|
| Origin AS | AS45474 NEXUSGUARD-AS-AP |
| Holder | Nexusguard Pte. Ltd. |
| Allocation | APNIC, Singapore (SG), allocated 1993-09-08 |
| Size | 256 addresses |
| Abuse contact | abuse@nexusguard.com |
What to fix
-
Warning
Reverse DNS is not delegated for 167.179.207.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.
Checks
Routing and RPKI Announced as 167.179.207.0/24 by AS45474.
- Pass: Announced as 167.179.207.0/24 by AS45474.
- Pass: 167.179.207.0/24 from AS45474 is RPKI valid.
- Pass: Seen by 100% of RIPE RIS peers.
| Route | 167.179.207.0/24 |
|---|---|
| Origin AS | AS45474 NEXUSGUARD-AS-AP - Nexusguard Pte. Ltd. RPKI valid |
| IRR route objects | APNIC, NTTCOM, RADB |
| Visibility (RIS peers) | 321 / 321 |
| First seen | 2022-02-28 |
| ROA prefix | Max length | Origin AS |
|---|---|---|
| 167.179.207.0/24 | /24 | AS45474 |
| 167.179.200.0/21 | /21 | AS45474 |
Source: RIPEstat (RIPE NCC RIS, Routinator)
Open in ASN & BGP prefix lookupReverse DNS Reverse DNS is not delegated for 167.179.207.0/24, so its addresses have no PTR records.
- Warning: Reverse DNS is not delegated for 167.179.207.0/24, so its addresses have no PTR records.
| Zone | Nameservers |
|---|---|
| 207.179.167.in-addr.arpa | Not delegated |
Registration Found at rdap.arin.net.
- Pass: Found at rdap.arin.net.
| Name | NEXUSGUARD-SG |
|---|---|
| Handle | 167.179.200.0 - 167.179.207.255 |
| Range | 167.179.200.0 – 167.179.207.255 |
| Country | SG |
| Status | active |
| Registered | 2026-01-08T07:45:22Z |
| Last changed | 2026-01-08T07:46:45Z |
| Abuse contact | abuse@nexusguard.com |
| Registry (RIR) | APNIC |
|---|---|
| Country | Singapore (SG) |
| Delegated on | 1993-09-08 |
| Status | Allocated |
| Delegated range | 167.179.200.0/21 (167.179.200.0 – 167.179.207.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | Nexusguard Pte. Ltd. | peering@nexusguard.com |
| administrative, technical | Nexusguard Pte Ltd administrator | abuse@nexusguard.com |
| abuse | IRT-NEXUSGUARD-SG | abuse@nexusguard.com |
Source: https://rdap.arin.net/registry/ip/167.179.207.0/24. 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: AS45474 is in PeeringDB as Nexusguard.
- Info: Peering policy: Selective.
- Info: Present at 9 internet exchanges with 11 ports (1T in total).
- Warning: No public NOC, policy or technical contact.
About the network that announces this space, so not in the fix list.
| Network | Nexusguard (Nexusguard) |
|---|---|
| AS number | AS45474 |
| Type | Network Services, Global |
| Website | https://www.nexusguard.com/ |
| IRR as-set | AS45474:AS-NEXUSGUARD |
| Prefixes (IPv4 / IPv6) | 1500 / 200 |
| Traffic | Mostly Inbound |
| Peering policy | Selective |
| Locations | Preferred |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-01-19 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup