Autonomous system
AS14369 NMAX
Unclassified APNIC
Summary
Nmax
isp telecom business
One of its blocks is registered to a name that is also its netname, with no company behind either.
What it's used for
- A regional provider's network. 4,352 addresses across two IPv4 prefixes plus a full
2604:a0c0::/32of IPv6, with two observed BGP neighbours.
Notable
65.79.240.0/20carries the netnameNMAX, registered toNmax.209.173.9.0/24carries the netnameJACKSON-BROADBANDand is registered toJACKSON-BROADBAND, the same string in both fields.- Six addresses were queried for reverse DNS and none returned a name.
Interesting
- A registrant field that repeats the netname exactly means nobody ever typed a legal entity into it. The record identifies a service, not a company, and whoever filed it treated the two fields as one. It is common enough in older records that it barely registers, and it makes the block untraceable to anyone who is not already inside.
- A hyphenated brand naming a town and a product is how small broadband operators name themselves everywhere, which makes the label both descriptive and useless for identification.
- A provider-sized
/32of IPv6 against a/20and a/24of IPv4 is the modern imbalance: the newer protocol is handed out in quantities that make the older one look like rationing, because it was. - Two neighbours and nothing answering a reverse lookup describes a network that sells connectivity and keeps its subscribers anonymous by default.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-16, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 4.35K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 3 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS14369- Registry name
- NMAX
- Registrant
- Nmax
- Abuse contact
- admin@nmax.net
- Registered
- 1999-12-03
- Last changed
- 2025-08-13
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 100% valid · 18 valid, 0 with no ROA
- ROAs
- 18 authorising AS14369
- ASPA
- 2 declared providers
- IRR
- 94% registered · 17 of 18 announcements
- Route objects
- 22 naming AS14369
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,783 prefixes, as published 2026-10-17. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere