diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..43ae0e2 --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +__pycache__/ +*.py[cod] diff --git a/Makefile b/Makefile index af82359..13acb84 100644 --- a/Makefile +++ b/Makefile @@ -1,8 +1,16 @@ -.PHONY: validate summary +.PHONY: validate test summary sync-iana-ipv4 validate: python3 scripts/validate.py + python3 -m unittest discover -s tests -v + +test: + python3 -m unittest discover -s tests -v + +sync-iana-ipv4: + python3 scripts/sync_iana_ipv4.py summary: @python3 -c "import csv,collections; r=list(csv.DictReader(open('data/entities.csv', encoding='utf-8'))); print(f'{len(r)} entities'); [print(f'{n:3} {k}') for k,n in sorted(collections.Counter(x['category'] for x in r).items())]" - @python3 -c "import csv; r=list(csv.DictReader(open('data/ip-addresses.csv', encoding='utf-8'))); print(f'{len(r)} IP address records: ' + ', '.join(x['address'] for x in r))" + @python3 -c "import csv; r=list(csv.DictReader(open('data/ip-addresses.csv', encoding='utf-8'))); print(f'{len(r)} exact IP records: ' + ', '.join(x['address'] for x in r))" + @python3 -c "import csv; t=list(csv.DictReader(open('data/iana-ipv4-top-level-ranges.csv', encoding='utf-8'))); s=list(csv.DictReader(open('data/iana-ipv4-special-ranges.csv', encoding='utf-8'))); print(f'{len(t)} IANA top-level IPv4 ranges; {len(s)} IANA special-purpose prefixes')" diff --git a/README.md b/README.md index 61f190a..385f852 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ A source-backed address book and evolving map of the organizations, coordination 1. Read the [first-round investigation](docs/02-first-round-investigation.md). 2. Browse the [human-readable address book](address-book/README.md). -3. Browse the range-based [`registry-ips/`](registry-ips/README.md), currently covering the investigated `0.0.0.0/8` and `1.1.1.0/24` ranges. +3. Browse the range-based [`registry-ips/`](registry-ips/README.md) and its [complete IANA IPv4 index](registry-ips/IPV4-INDEX.md), covering every top-level IPv4 `/8` plus all IANA special-purpose IPv4 prefixes. 4. Start the exact-address map with [0.0.0.0 and 1.1.1.1](address-book/ip-addresses.md). 5. Use [`data/entities.csv`](data/entities.csv) and [`data/ip-addresses.csv`](data/ip-addresses.csv) for machine-readable records. 6. Review the [next research round](research/next-round.md) and [IP network roadmap](research/ip-network-roadmap.md). diff --git a/data/README.md b/data/README.md index e13c613..e1cd83e 100644 --- a/data/README.md +++ b/data/README.md @@ -22,3 +22,10 @@ CSV was chosen for round 1 because it is inspectable in Git, opens in spreadsheets, and requires no custom parser. If nested relationships become central, introduce versioned YAML or JSON without deleting CSV history. The IP-specific columns are documented in [`docs/04-ip-address-model.md`](../docs/04-ip-address-model.md). + +## Authoritative IANA IPv4 datasets + +- `iana-ipv4-top-level-ranges.csv` normalizes all 256 records from the IANA IPv4 Address Space Registry. Together they cover the complete IPv4 address space at `/8` granularity. +- `iana-ipv4-special-ranges.csv` normalizes and expands all IANA IPv4 Special-Purpose Address Registry entries, including source/destination, forwarding, global-reachability, and protocol-reservation properties. + +Both datasets include source URL, verification date, and the corresponding Markdown filename. They are generated by [`scripts/sync_iana_ipv4.py`](../scripts/sync_iana_ipv4.py); do not treat top-level registry authority as exact-address ownership or current route operation. diff --git a/data/iana-ipv4-special-ranges.csv b/data/iana-ipv4-special-ranges.csv new file mode 100644 index 0000000..568976b --- /dev/null +++ b/data/iana-ipv4-special-ranges.csv @@ -0,0 +1,27 @@ +prefix,name,rfc,allocation_date,termination_date,source,destination,forwardable,globally_reachable,reserved_by_protocol,source_url,verified_at,filename +0.0.0.0/8,This network,"[RFC791], Section 3.2",1981-09,N/A,True,False,False,False,True,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,000-000-000-000--08--iana.md +0.0.0.0/32,This host on this network,"[RFC1122], Section 3.2.1.3",1981-09,N/A,True,False,False,False,True,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,000-000-000-000--32--iana-special.md +10.0.0.0/8,Private-Use,[RFC1918],1996-02,N/A,True,True,True,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,010-000-000-000--08--iana-special.md +100.64.0.0/10,Shared Address Space,[RFC6598],2012-04,N/A,True,True,True,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,100-064-000-000--10--iana-special.md +127.0.0.0/8,Loopback,"[RFC1122], Section 3.2.1.3",1981-09,N/A,False [1],False [1],False [1],False [1],True,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,127-000-000-000--08--iana-special.md +169.254.0.0/16,Link Local,[RFC3927],2005-05,N/A,True,True,False,False,True,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,169-254-000-000--16--iana-special.md +172.16.0.0/12,Private-Use,[RFC1918],1996-02,N/A,True,True,True,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,172-016-000-000--12--iana-special.md +192.0.0.0/24,IETF Protocol Assignments,"[RFC6890], Section 2.1",2010-01,N/A,False,False,False,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-000-000-000--24--iana-special.md +192.0.0.0/29,IPv4 Service Continuity Prefix,[RFC7335],2011-06,N/A,True,True,True,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-000-000-000--29--iana-special.md +192.0.0.8/32,IPv4 dummy address,[RFC7600],2015-03,N/A,True,False,False,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-000-000-008--32--iana-special.md +192.0.0.9/32,Port Control Protocol Anycast,[RFC7723],2015-10,N/A,True,True,True,True,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-000-000-009--32--iana-special.md +192.0.0.10/32,Traversal Using Relays around NAT Anycast,[RFC8155],2017-02,N/A,True,True,True,True,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-000-000-010--32--iana-special.md +192.0.0.170/32,NAT64/DNS64 Discovery,"[RFC8880][RFC7050], Section 2.2",2013-02,N/A,False,False,False,False,True,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-000-000-170--32--iana-special.md +192.0.0.171/32,NAT64/DNS64 Discovery,"[RFC8880][RFC7050], Section 2.2",2013-02,N/A,False,False,False,False,True,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-000-000-171--32--iana-special.md +192.0.2.0/24,Documentation (TEST-NET-1),[RFC5737],2010-01,N/A,False,False,False,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-000-002-000--24--iana-special.md +192.31.196.0/24,AS112-v4,[RFC7535],2014-12,N/A,True,True,True,True,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-031-196-000--24--iana-special.md +192.52.193.0/24,AMT,[RFC7450],2014-12,N/A,True,True,True,True,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-052-193-000--24--iana-special.md +192.88.99.0/24,Deprecated (6to4 Relay Anycast),[RFC7526],2001-06,2015-03,,,,,,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-088-099-000--24--iana-special.md +192.88.99.2/32,6a44-relay anycast address,[RFC6751],2012-10,N/A,True,True,True,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-088-099-002--32--iana-special.md +192.168.0.0/16,Private-Use,[RFC1918],1996-02,N/A,True,True,True,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-168-000-000--16--iana-special.md +192.175.48.0/24,Direct Delegation AS112 Service,[RFC7534],1996-01,N/A,True,True,True,True,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,192-175-048-000--24--iana-special.md +198.18.0.0/15,Benchmarking,[RFC2544],1999-03,N/A,True,True,True,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,198-018-000-000--15--iana-special.md +198.51.100.0/24,Documentation (TEST-NET-2),[RFC5737],2010-01,N/A,False,False,False,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,198-051-100-000--24--iana-special.md +203.0.113.0/24,Documentation (TEST-NET-3),[RFC5737],2010-01,N/A,False,False,False,False,False,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,203-000-113-000--24--iana-special.md +240.0.0.0/4,Reserved,"[RFC1112], Section 4",1989-08,N/A,False,False,False,False,True,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,240-000-000-000--04--iana-special.md +255.255.255.255/32,Limited Broadcast,"[RFC8190] [RFC919], Section 7",1984-10,N/A,False,True,False,False,True,https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml,2026-07-22,255-255-255-255--32--iana-special.md diff --git a/data/iana-ipv4-top-level-ranges.csv b/data/iana-ipv4-top-level-ranges.csv new file mode 100644 index 0000000..77ccdf8 --- /dev/null +++ b/data/iana-ipv4-top-level-ranges.csv @@ -0,0 +1,257 @@ +prefix,designation,registry,status,allocation_date,whois,rdap,note,source_url,verified_at,filename +0.0.0.0/8,IANA - Local Identification,iana,reserved,1981-09,,,[2][3],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,000-000-000-000--08--iana.md +1.0.0.0/8,APNIC,apnic,allocated,2010-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,001-000-000-000--08--apnic.md +2.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2009-09,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,002-000-000-000--08--ripe-ncc.md +3.0.0.0/8,Administered by ARIN,arin,legacy,1994-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,003-000-000-000--08--arin.md +4.0.0.0/8,Administered by ARIN,arin,legacy,1992-12,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,004-000-000-000--08--arin.md +5.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2010-11,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,005-000-000-000--08--ripe-ncc.md +6.0.0.0/8,Army Information Systems Center,arin,legacy,1994-02,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,006-000-000-000--08--arin.md +7.0.0.0/8,Administered by ARIN,arin,legacy,1995-04,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,007-000-000-000--08--arin.md +8.0.0.0/8,Administered by ARIN,arin,legacy,1992-12,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,008-000-000-000--08--arin.md +9.0.0.0/8,Administered by ARIN,arin,legacy,1992-08,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,009-000-000-000--08--arin.md +10.0.0.0/8,IANA - Private Use,iana,reserved,1995-06,,,[4],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,010-000-000-000--08--iana.md +11.0.0.0/8,DoD Intel Information Systems,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,011-000-000-000--08--arin.md +12.0.0.0/8,AT&T Bell Laboratories,arin,legacy,1995-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,012-000-000-000--08--arin.md +13.0.0.0/8,Administered by ARIN,arin,legacy,1991-09,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,013-000-000-000--08--arin.md +14.0.0.0/8,APNIC,apnic,allocated,2010-04,whois.apnic.net,https://rdap.apnic.net/,[5],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,014-000-000-000--08--apnic.md +15.0.0.0/8,Administered by ARIN,arin,legacy,1994-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,015-000-000-000--08--arin.md +16.0.0.0/8,Administered by ARIN,arin,legacy,1994-11,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,016-000-000-000--08--arin.md +17.0.0.0/8,Apple Computer Inc.,arin,legacy,1992-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,017-000-000-000--08--arin.md +18.0.0.0/8,Administered by ARIN,arin,legacy,1994-01,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,018-000-000-000--08--arin.md +19.0.0.0/8,Ford Motor Company,arin,legacy,1995-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,019-000-000-000--08--arin.md +20.0.0.0/8,Administered by ARIN,arin,legacy,1994-10,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,020-000-000-000--08--arin.md +21.0.0.0/8,DDN-RVN,arin,legacy,1991-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,021-000-000-000--08--arin.md +22.0.0.0/8,Defense Information Systems Agency,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,022-000-000-000--08--arin.md +23.0.0.0/8,ARIN,arin,allocated,2010-11,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,023-000-000-000--08--arin.md +24.0.0.0/8,ARIN,arin,allocated,2001-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,024-000-000-000--08--arin.md +25.0.0.0/8,Administered by RIPE NCC,ripe-ncc,legacy,1995-01,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,025-000-000-000--08--ripe-ncc.md +26.0.0.0/8,Defense Information Systems Agency,arin,legacy,1995-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,026-000-000-000--08--arin.md +27.0.0.0/8,APNIC,apnic,allocated,2010-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,027-000-000-000--08--apnic.md +28.0.0.0/8,DSI-North,arin,legacy,1992-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,028-000-000-000--08--arin.md +29.0.0.0/8,Defense Information Systems Agency,arin,legacy,1991-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,029-000-000-000--08--arin.md +30.0.0.0/8,Defense Information Systems Agency,arin,legacy,1991-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,030-000-000-000--08--arin.md +31.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2010-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,031-000-000-000--08--ripe-ncc.md +32.0.0.0/8,Administered by ARIN,arin,legacy,1994-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,032-000-000-000--08--arin.md +33.0.0.0/8,DLA Systems Automation Center,arin,legacy,1991-01,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,033-000-000-000--08--arin.md +34.0.0.0/8,Administered by ARIN,arin,legacy,1993-03,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,034-000-000-000--08--arin.md +35.0.0.0/8,Administered by ARIN,arin,legacy,1994-04,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,035-000-000-000--08--arin.md +36.0.0.0/8,APNIC,apnic,allocated,2010-10,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,036-000-000-000--08--apnic.md +37.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2010-11,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,037-000-000-000--08--ripe-ncc.md +38.0.0.0/8,"PSINet, Inc.",arin,legacy,1994-09,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,038-000-000-000--08--arin.md +39.0.0.0/8,APNIC,apnic,allocated,2011-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,039-000-000-000--08--apnic.md +40.0.0.0/8,Administered by ARIN,arin,legacy,1994-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,040-000-000-000--08--arin.md +41.0.0.0/8,AFRINIC,afrinic,allocated,2005-04,whois.afrinic.net,https://rdap.afrinic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,041-000-000-000--08--afrinic.md +42.0.0.0/8,APNIC,apnic,allocated,2010-10,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,042-000-000-000--08--apnic.md +43.0.0.0/8,Administered by APNIC,apnic,legacy,1991-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,043-000-000-000--08--apnic.md +44.0.0.0/8,Administered by ARIN,arin,legacy,1992-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,044-000-000-000--08--arin.md +45.0.0.0/8,Administered by ARIN,arin,legacy,1995-01,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,045-000-000-000--08--arin.md +46.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2009-09,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,046-000-000-000--08--ripe-ncc.md +47.0.0.0/8,Administered by ARIN,arin,legacy,1991-01,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,047-000-000-000--08--arin.md +48.0.0.0/8,Administered by ARIN,arin,legacy,1995-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,048-000-000-000--08--arin.md +49.0.0.0/8,APNIC,apnic,allocated,2010-08,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,049-000-000-000--08--apnic.md +50.0.0.0/8,ARIN,arin,allocated,2010-02,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,050-000-000-000--08--arin.md +51.0.0.0/8,Administered by RIPE NCC,ripe-ncc,legacy,1994-08,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,051-000-000-000--08--ripe-ncc.md +52.0.0.0/8,Administered by ARIN,arin,legacy,1991-12,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,052-000-000-000--08--arin.md +53.0.0.0/8,Daimler AG,ripe-ncc,legacy,1993-10,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,053-000-000-000--08--ripe-ncc.md +54.0.0.0/8,Administered by ARIN,arin,legacy,1992-03,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,054-000-000-000--08--arin.md +55.0.0.0/8,DoD Network Information Center,arin,legacy,1995-04,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,055-000-000-000--08--arin.md +56.0.0.0/8,Administered by ARIN,arin,legacy,1994-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,056-000-000-000--08--arin.md +57.0.0.0/8,Administered by RIPE NCC,ripe-ncc,legacy,1995-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,057-000-000-000--08--ripe-ncc.md +58.0.0.0/8,APNIC,apnic,allocated,2004-04,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,058-000-000-000--08--apnic.md +59.0.0.0/8,APNIC,apnic,allocated,2004-04,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,059-000-000-000--08--apnic.md +60.0.0.0/8,APNIC,apnic,allocated,2003-04,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,060-000-000-000--08--apnic.md +61.0.0.0/8,APNIC,apnic,allocated,1997-04,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,061-000-000-000--08--apnic.md +62.0.0.0/8,RIPE NCC,ripe-ncc,allocated,1997-04,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,062-000-000-000--08--ripe-ncc.md +63.0.0.0/8,ARIN,arin,allocated,1997-04,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,063-000-000-000--08--arin.md +64.0.0.0/8,ARIN,arin,allocated,1999-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,064-000-000-000--08--arin.md +65.0.0.0/8,ARIN,arin,allocated,2000-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,065-000-000-000--08--arin.md +66.0.0.0/8,ARIN,arin,allocated,2000-07,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,066-000-000-000--08--arin.md +67.0.0.0/8,ARIN,arin,allocated,2001-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,067-000-000-000--08--arin.md +68.0.0.0/8,ARIN,arin,allocated,2001-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,068-000-000-000--08--arin.md +69.0.0.0/8,ARIN,arin,allocated,2002-08,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,069-000-000-000--08--arin.md +70.0.0.0/8,ARIN,arin,allocated,2004-01,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,070-000-000-000--08--arin.md +71.0.0.0/8,ARIN,arin,allocated,2004-08,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,071-000-000-000--08--arin.md +72.0.0.0/8,ARIN,arin,allocated,2004-08,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,072-000-000-000--08--arin.md +73.0.0.0/8,ARIN,arin,allocated,2005-03,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,073-000-000-000--08--arin.md +74.0.0.0/8,ARIN,arin,allocated,2005-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,074-000-000-000--08--arin.md +75.0.0.0/8,ARIN,arin,allocated,2005-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,075-000-000-000--08--arin.md +76.0.0.0/8,ARIN,arin,allocated,2005-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,076-000-000-000--08--arin.md +77.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2006-08,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,077-000-000-000--08--ripe-ncc.md +78.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2006-08,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,078-000-000-000--08--ripe-ncc.md +79.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2006-08,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,079-000-000-000--08--ripe-ncc.md +80.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2001-04,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,080-000-000-000--08--ripe-ncc.md +81.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2001-04,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,081-000-000-000--08--ripe-ncc.md +82.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2002-11,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,082-000-000-000--08--ripe-ncc.md +83.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2003-11,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,083-000-000-000--08--ripe-ncc.md +84.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2003-11,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,084-000-000-000--08--ripe-ncc.md +85.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2004-04,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,085-000-000-000--08--ripe-ncc.md +86.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2004-04,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,086-000-000-000--08--ripe-ncc.md +87.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2004-04,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,087-000-000-000--08--ripe-ncc.md +88.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2004-04,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,088-000-000-000--08--ripe-ncc.md +89.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2005-06,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,089-000-000-000--08--ripe-ncc.md +90.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2005-06,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,090-000-000-000--08--ripe-ncc.md +91.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2005-06,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,091-000-000-000--08--ripe-ncc.md +92.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2007-03,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,092-000-000-000--08--ripe-ncc.md +93.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2007-03,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,093-000-000-000--08--ripe-ncc.md +94.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2007-07,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,094-000-000-000--08--ripe-ncc.md +95.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2007-07,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,095-000-000-000--08--ripe-ncc.md +96.0.0.0/8,ARIN,arin,allocated,2006-10,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,096-000-000-000--08--arin.md +97.0.0.0/8,ARIN,arin,allocated,2006-10,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,097-000-000-000--08--arin.md +98.0.0.0/8,ARIN,arin,allocated,2006-10,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,098-000-000-000--08--arin.md +99.0.0.0/8,ARIN,arin,allocated,2006-10,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,099-000-000-000--08--arin.md +100.0.0.0/8,ARIN,arin,allocated,2010-11,whois.arin.net,https://rdap.arin.net/registry,[6],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,100-000-000-000--08--arin.md +101.0.0.0/8,APNIC,apnic,allocated,2010-08,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,101-000-000-000--08--apnic.md +102.0.0.0/8,AFRINIC,afrinic,allocated,2011-02,whois.afrinic.net,https://rdap.afrinic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,102-000-000-000--08--afrinic.md +103.0.0.0/8,APNIC,apnic,allocated,2011-02,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,103-000-000-000--08--apnic.md +104.0.0.0/8,ARIN,arin,allocated,2011-02,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,104-000-000-000--08--arin.md +105.0.0.0/8,AFRINIC,afrinic,allocated,2010-11,whois.afrinic.net,https://rdap.afrinic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,105-000-000-000--08--afrinic.md +106.0.0.0/8,APNIC,apnic,allocated,2011-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,106-000-000-000--08--apnic.md +107.0.0.0/8,ARIN,arin,allocated,2010-02,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,107-000-000-000--08--arin.md +108.0.0.0/8,ARIN,arin,allocated,2008-12,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,108-000-000-000--08--arin.md +109.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2009-01,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,109-000-000-000--08--ripe-ncc.md +110.0.0.0/8,APNIC,apnic,allocated,2008-11,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,110-000-000-000--08--apnic.md +111.0.0.0/8,APNIC,apnic,allocated,2008-11,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,111-000-000-000--08--apnic.md +112.0.0.0/8,APNIC,apnic,allocated,2008-05,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,112-000-000-000--08--apnic.md +113.0.0.0/8,APNIC,apnic,allocated,2008-05,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,113-000-000-000--08--apnic.md +114.0.0.0/8,APNIC,apnic,allocated,2007-10,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,114-000-000-000--08--apnic.md +115.0.0.0/8,APNIC,apnic,allocated,2007-10,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,115-000-000-000--08--apnic.md +116.0.0.0/8,APNIC,apnic,allocated,2007-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,116-000-000-000--08--apnic.md +117.0.0.0/8,APNIC,apnic,allocated,2007-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,117-000-000-000--08--apnic.md +118.0.0.0/8,APNIC,apnic,allocated,2007-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,118-000-000-000--08--apnic.md +119.0.0.0/8,APNIC,apnic,allocated,2007-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,119-000-000-000--08--apnic.md +120.0.0.0/8,APNIC,apnic,allocated,2007-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,120-000-000-000--08--apnic.md +121.0.0.0/8,APNIC,apnic,allocated,2006-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,121-000-000-000--08--apnic.md +122.0.0.0/8,APNIC,apnic,allocated,2006-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,122-000-000-000--08--apnic.md +123.0.0.0/8,APNIC,apnic,allocated,2006-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,123-000-000-000--08--apnic.md +124.0.0.0/8,APNIC,apnic,allocated,2005-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,124-000-000-000--08--apnic.md +125.0.0.0/8,APNIC,apnic,allocated,2005-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,125-000-000-000--08--apnic.md +126.0.0.0/8,APNIC,apnic,allocated,2005-01,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,126-000-000-000--08--apnic.md +127.0.0.0/8,IANA - Loopback,iana,reserved,1981-09,,,[7],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,127-000-000-000--08--iana.md +128.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,128-000-000-000--08--arin.md +129.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,129-000-000-000--08--arin.md +130.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,130-000-000-000--08--arin.md +131.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,131-000-000-000--08--arin.md +132.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,132-000-000-000--08--arin.md +133.0.0.0/8,Administered by APNIC,apnic,legacy,1997-03,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,133-000-000-000--08--apnic.md +134.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,134-000-000-000--08--arin.md +135.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,135-000-000-000--08--arin.md +136.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,136-000-000-000--08--arin.md +137.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,137-000-000-000--08--arin.md +138.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,138-000-000-000--08--arin.md +139.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,139-000-000-000--08--arin.md +140.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,140-000-000-000--08--arin.md +141.0.0.0/8,Administered by RIPE NCC,ripe-ncc,legacy,1993-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,141-000-000-000--08--ripe-ncc.md +142.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,142-000-000-000--08--arin.md +143.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,143-000-000-000--08--arin.md +144.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,144-000-000-000--08--arin.md +145.0.0.0/8,Administered by RIPE NCC,ripe-ncc,legacy,1993-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,145-000-000-000--08--ripe-ncc.md +146.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,146-000-000-000--08--arin.md +147.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,147-000-000-000--08--arin.md +148.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,148-000-000-000--08--arin.md +149.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,149-000-000-000--08--arin.md +150.0.0.0/8,Administered by APNIC,apnic,legacy,1993-05,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,150-000-000-000--08--apnic.md +151.0.0.0/8,Administered by RIPE NCC,ripe-ncc,legacy,1993-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,151-000-000-000--08--ripe-ncc.md +152.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,152-000-000-000--08--arin.md +153.0.0.0/8,Administered by APNIC,apnic,legacy,1993-05,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,153-000-000-000--08--apnic.md +154.0.0.0/8,Administered by AFRINIC,afrinic,legacy,1993-05,whois.afrinic.net,https://rdap.afrinic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,154-000-000-000--08--afrinic.md +155.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,155-000-000-000--08--arin.md +156.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,156-000-000-000--08--arin.md +157.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,157-000-000-000--08--arin.md +158.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,158-000-000-000--08--arin.md +159.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,159-000-000-000--08--arin.md +160.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,160-000-000-000--08--arin.md +161.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,161-000-000-000--08--arin.md +162.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,162-000-000-000--08--arin.md +163.0.0.0/8,Administered by APNIC,apnic,legacy,1993-05,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,163-000-000-000--08--apnic.md +164.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,164-000-000-000--08--arin.md +165.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,165-000-000-000--08--arin.md +166.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,166-000-000-000--08--arin.md +167.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,167-000-000-000--08--arin.md +168.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,168-000-000-000--08--arin.md +169.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,[8],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,169-000-000-000--08--arin.md +170.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,170-000-000-000--08--arin.md +171.0.0.0/8,Administered by APNIC,apnic,legacy,1993-05,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,171-000-000-000--08--apnic.md +172.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,[9],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,172-000-000-000--08--arin.md +173.0.0.0/8,ARIN,arin,allocated,2008-02,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,173-000-000-000--08--arin.md +174.0.0.0/8,ARIN,arin,allocated,2008-02,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,174-000-000-000--08--arin.md +175.0.0.0/8,APNIC,apnic,allocated,2009-08,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,175-000-000-000--08--apnic.md +176.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2010-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,176-000-000-000--08--ripe-ncc.md +177.0.0.0/8,LACNIC,lacnic,allocated,2010-06,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,177-000-000-000--08--lacnic.md +178.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2009-01,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,178-000-000-000--08--ripe-ncc.md +179.0.0.0/8,LACNIC,lacnic,allocated,2011-02,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,179-000-000-000--08--lacnic.md +180.0.0.0/8,APNIC,apnic,allocated,2009-04,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,180-000-000-000--08--apnic.md +181.0.0.0/8,LACNIC,lacnic,allocated,2010-06,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,181-000-000-000--08--lacnic.md +182.0.0.0/8,APNIC,apnic,allocated,2009-08,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,182-000-000-000--08--apnic.md +183.0.0.0/8,APNIC,apnic,allocated,2009-04,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,183-000-000-000--08--apnic.md +184.0.0.0/8,ARIN,arin,allocated,2008-12,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,184-000-000-000--08--arin.md +185.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2011-02,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,185-000-000-000--08--ripe-ncc.md +186.0.0.0/8,LACNIC,lacnic,allocated,2007-09,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,186-000-000-000--08--lacnic.md +187.0.0.0/8,LACNIC,lacnic,allocated,2007-09,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,187-000-000-000--08--lacnic.md +188.0.0.0/8,Administered by RIPE NCC,ripe-ncc,legacy,1993-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,188-000-000-000--08--ripe-ncc.md +189.0.0.0/8,LACNIC,lacnic,allocated,1995-06,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,189-000-000-000--08--lacnic.md +190.0.0.0/8,LACNIC,lacnic,allocated,1995-06,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,190-000-000-000--08--lacnic.md +191.0.0.0/8,Administered by LACNIC,lacnic,legacy,1993-05,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,191-000-000-000--08--lacnic.md +192.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,[10][11],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,192-000-000-000--08--arin.md +193.0.0.0/8,RIPE NCC,ripe-ncc,allocated,1993-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,193-000-000-000--08--ripe-ncc.md +194.0.0.0/8,RIPE NCC,ripe-ncc,allocated,1993-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,194-000-000-000--08--ripe-ncc.md +195.0.0.0/8,RIPE NCC,ripe-ncc,allocated,1993-05,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,195-000-000-000--08--ripe-ncc.md +196.0.0.0/8,Administered by AFRINIC,afrinic,legacy,1993-05,whois.afrinic.net,https://rdap.afrinic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,196-000-000-000--08--afrinic.md +197.0.0.0/8,AFRINIC,afrinic,allocated,2008-10,whois.afrinic.net,https://rdap.afrinic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,197-000-000-000--08--afrinic.md +198.0.0.0/8,Administered by ARIN,arin,legacy,1993-05,whois.arin.net,https://rdap.arin.net/registry,[12],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,198-000-000-000--08--arin.md +199.0.0.0/8,ARIN,arin,allocated,1993-05,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,199-000-000-000--08--arin.md +200.0.0.0/8,LACNIC,lacnic,allocated,2002-11,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,200-000-000-000--08--lacnic.md +201.0.0.0/8,LACNIC,lacnic,allocated,2003-04,whois.lacnic.net,https://rdap.lacnic.net/rdap/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,201-000-000-000--08--lacnic.md +202.0.0.0/8,APNIC,apnic,allocated,1993-05,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,202-000-000-000--08--apnic.md +203.0.0.0/8,APNIC,apnic,allocated,1993-05,whois.apnic.net,https://rdap.apnic.net/,[13],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,203-000-000-000--08--apnic.md +204.0.0.0/8,ARIN,arin,allocated,1994-03,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,204-000-000-000--08--arin.md +205.0.0.0/8,ARIN,arin,allocated,1994-03,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,205-000-000-000--08--arin.md +206.0.0.0/8,ARIN,arin,allocated,1995-04,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,206-000-000-000--08--arin.md +207.0.0.0/8,ARIN,arin,allocated,1995-11,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,207-000-000-000--08--arin.md +208.0.0.0/8,ARIN,arin,allocated,1996-04,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,208-000-000-000--08--arin.md +209.0.0.0/8,ARIN,arin,allocated,1996-06,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,209-000-000-000--08--arin.md +210.0.0.0/8,APNIC,apnic,allocated,1996-06,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,210-000-000-000--08--apnic.md +211.0.0.0/8,APNIC,apnic,allocated,1996-06,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,211-000-000-000--08--apnic.md +212.0.0.0/8,RIPE NCC,ripe-ncc,allocated,1997-10,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,212-000-000-000--08--ripe-ncc.md +213.0.0.0/8,RIPE NCC,ripe-ncc,allocated,1993-10,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,213-000-000-000--08--ripe-ncc.md +214.0.0.0/8,US-DOD,arin,legacy,1998-03,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,214-000-000-000--08--arin.md +215.0.0.0/8,US-DOD,arin,legacy,1998-03,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,215-000-000-000--08--arin.md +216.0.0.0/8,ARIN,arin,allocated,1998-04,whois.arin.net,https://rdap.arin.net/registry,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,216-000-000-000--08--arin.md +217.0.0.0/8,RIPE NCC,ripe-ncc,allocated,2000-06,whois.ripe.net,https://rdap.db.ripe.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,217-000-000-000--08--ripe-ncc.md +218.0.0.0/8,APNIC,apnic,allocated,2000-12,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,218-000-000-000--08--apnic.md +219.0.0.0/8,APNIC,apnic,allocated,2001-09,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,219-000-000-000--08--apnic.md +220.0.0.0/8,APNIC,apnic,allocated,2001-12,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,220-000-000-000--08--apnic.md +221.0.0.0/8,APNIC,apnic,allocated,2002-07,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,221-000-000-000--08--apnic.md +222.0.0.0/8,APNIC,apnic,allocated,2003-02,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,222-000-000-000--08--apnic.md +223.0.0.0/8,APNIC,apnic,allocated,2010-04,whois.apnic.net,https://rdap.apnic.net/,,https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,223-000-000-000--08--apnic.md +224.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,224-000-000-000--08--iana.md +225.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,225-000-000-000--08--iana.md +226.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,226-000-000-000--08--iana.md +227.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,227-000-000-000--08--iana.md +228.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,228-000-000-000--08--iana.md +229.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,229-000-000-000--08--iana.md +230.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,230-000-000-000--08--iana.md +231.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,231-000-000-000--08--iana.md +232.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,232-000-000-000--08--iana.md +233.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,233-000-000-000--08--iana.md +234.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14][15],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,234-000-000-000--08--iana.md +235.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,235-000-000-000--08--iana.md +236.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,236-000-000-000--08--iana.md +237.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,237-000-000-000--08--iana.md +238.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,238-000-000-000--08--iana.md +239.0.0.0/8,Multicast,iana,reserved,1981-09,,,[14][16],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,239-000-000-000--08--iana.md +240.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,240-000-000-000--08--iana.md +241.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,241-000-000-000--08--iana.md +242.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,242-000-000-000--08--iana.md +243.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,243-000-000-000--08--iana.md +244.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,244-000-000-000--08--iana.md +245.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,245-000-000-000--08--iana.md +246.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,246-000-000-000--08--iana.md +247.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,247-000-000-000--08--iana.md +248.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,248-000-000-000--08--iana.md +249.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,249-000-000-000--08--iana.md +250.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,250-000-000-000--08--iana.md +251.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,251-000-000-000--08--iana.md +252.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,252-000-000-000--08--iana.md +253.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,253-000-000-000--08--iana.md +254.0.0.0/8,Future use,iana,reserved,1981-09,,,[17],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,254-000-000-000--08--iana.md +255.0.0.0/8,Future use,iana,reserved,1981-09,,,[17][18],https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml,2026-07-22,255-000-000-000--08--iana.md diff --git a/registry-ips/000-000-000-000--32--iana-special.md b/registry-ips/000-000-000-000--32--iana-special.md new file mode 100644 index 0000000..8ee38c1 --- /dev/null +++ b/registry-ips/000-000-000-000--32--iana-special.md @@ -0,0 +1,28 @@ + +# 0.0.0.0/32 — This host on this network + +## Who is this IP range? + +IANA identifies **0.0.0.0/32** as **This host on this network** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `0.0.0.0/32` +- **Name:** This host on this network +- **RFC/reference:** [RFC1122], Section 3.2.1.3 +- **Allocation date:** 1981-09 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** True +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/001-000-000-000--08--apnic.md b/registry-ips/001-000-000-000--08--apnic.md new file mode 100644 index 0000000..453cd69 --- /dev/null +++ b/registry-ips/001-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 1.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **1.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `1.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/002-000-000-000--08--ripe-ncc.md b/registry-ips/002-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..379d1a4 --- /dev/null +++ b/registry-ips/002-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 2.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **2.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `2.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2009-09 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/003-000-000-000--08--arin.md b/registry-ips/003-000-000-000--08--arin.md new file mode 100644 index 0000000..97157f1 --- /dev/null +++ b/registry-ips/003-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 3.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **3.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `3.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/004-000-000-000--08--arin.md b/registry-ips/004-000-000-000--08--arin.md new file mode 100644 index 0000000..7e53c7d --- /dev/null +++ b/registry-ips/004-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 4.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **4.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `4.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1992-12 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/005-000-000-000--08--ripe-ncc.md b/registry-ips/005-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..aa55b25 --- /dev/null +++ b/registry-ips/005-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 5.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **5.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `5.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-11 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/006-000-000-000--08--arin.md b/registry-ips/006-000-000-000--08--arin.md new file mode 100644 index 0000000..1573e60 --- /dev/null +++ b/registry-ips/006-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 6.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **6.0.0.0/8** to **Army Information Systems Center** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `6.0.0.0/8` +- **IANA designation:** Army Information Systems Center +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-02 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/007-000-000-000--08--arin.md b/registry-ips/007-000-000-000--08--arin.md new file mode 100644 index 0000000..2a8c4ef --- /dev/null +++ b/registry-ips/007-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 7.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **7.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `7.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-04 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/008-000-000-000--08--arin.md b/registry-ips/008-000-000-000--08--arin.md new file mode 100644 index 0000000..4f9d5af --- /dev/null +++ b/registry-ips/008-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 8.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **8.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `8.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1992-12 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/009-000-000-000--08--arin.md b/registry-ips/009-000-000-000--08--arin.md new file mode 100644 index 0000000..441da9b --- /dev/null +++ b/registry-ips/009-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 9.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **9.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `9.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1992-08 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/010-000-000-000--08--iana-special.md b/registry-ips/010-000-000-000--08--iana-special.md new file mode 100644 index 0000000..e3b1020 --- /dev/null +++ b/registry-ips/010-000-000-000--08--iana-special.md @@ -0,0 +1,28 @@ + +# 10.0.0.0/8 — Private-Use + +## Who is this IP range? + +IANA identifies **10.0.0.0/8** as **Private-Use** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `10.0.0.0/8` +- **Name:** Private-Use +- **RFC/reference:** [RFC1918] +- **Allocation date:** 1996-02 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/010-000-000-000--08--iana.md b/registry-ips/010-000-000-000--08--iana.md new file mode 100644 index 0000000..f43ef35 --- /dev/null +++ b/registry-ips/010-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 10.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **10.0.0.0/8** as **IANA - Private Use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `10.0.0.0/8` +- **IANA designation:** IANA - Private Use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1995-06 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [4] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/011-000-000-000--08--arin.md b/registry-ips/011-000-000-000--08--arin.md new file mode 100644 index 0000000..bcc0c30 --- /dev/null +++ b/registry-ips/011-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 11.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **11.0.0.0/8** to **DoD Intel Information Systems** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `11.0.0.0/8` +- **IANA designation:** DoD Intel Information Systems +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/012-000-000-000--08--arin.md b/registry-ips/012-000-000-000--08--arin.md new file mode 100644 index 0000000..b17d62b --- /dev/null +++ b/registry-ips/012-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 12.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **12.0.0.0/8** to **AT&T Bell Laboratories** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `12.0.0.0/8` +- **IANA designation:** AT&T Bell Laboratories +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/013-000-000-000--08--arin.md b/registry-ips/013-000-000-000--08--arin.md new file mode 100644 index 0000000..b38efc2 --- /dev/null +++ b/registry-ips/013-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 13.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **13.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `13.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1991-09 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/014-000-000-000--08--apnic.md b/registry-ips/014-000-000-000--08--apnic.md new file mode 100644 index 0000000..cdbf622 --- /dev/null +++ b/registry-ips/014-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 14.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **14.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `14.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-04 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** [5] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/015-000-000-000--08--arin.md b/registry-ips/015-000-000-000--08--arin.md new file mode 100644 index 0000000..ef08375 --- /dev/null +++ b/registry-ips/015-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 15.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **15.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `15.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/016-000-000-000--08--arin.md b/registry-ips/016-000-000-000--08--arin.md new file mode 100644 index 0000000..4c69969 --- /dev/null +++ b/registry-ips/016-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 16.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **16.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `16.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-11 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/017-000-000-000--08--arin.md b/registry-ips/017-000-000-000--08--arin.md new file mode 100644 index 0000000..8bb6d2e --- /dev/null +++ b/registry-ips/017-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 17.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **17.0.0.0/8** to **Apple Computer Inc.** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `17.0.0.0/8` +- **IANA designation:** Apple Computer Inc. +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1992-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/018-000-000-000--08--arin.md b/registry-ips/018-000-000-000--08--arin.md new file mode 100644 index 0000000..2ff4574 --- /dev/null +++ b/registry-ips/018-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 18.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **18.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `18.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-01 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/019-000-000-000--08--arin.md b/registry-ips/019-000-000-000--08--arin.md new file mode 100644 index 0000000..a303a1f --- /dev/null +++ b/registry-ips/019-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 19.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **19.0.0.0/8** to **Ford Motor Company** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `19.0.0.0/8` +- **IANA designation:** Ford Motor Company +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/020-000-000-000--08--arin.md b/registry-ips/020-000-000-000--08--arin.md new file mode 100644 index 0000000..30fb664 --- /dev/null +++ b/registry-ips/020-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 20.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **20.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `20.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-10 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/021-000-000-000--08--arin.md b/registry-ips/021-000-000-000--08--arin.md new file mode 100644 index 0000000..90a4710 --- /dev/null +++ b/registry-ips/021-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 21.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **21.0.0.0/8** to **DDN-RVN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `21.0.0.0/8` +- **IANA designation:** DDN-RVN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1991-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/022-000-000-000--08--arin.md b/registry-ips/022-000-000-000--08--arin.md new file mode 100644 index 0000000..2a66abe --- /dev/null +++ b/registry-ips/022-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 22.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **22.0.0.0/8** to **Defense Information Systems Agency** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `22.0.0.0/8` +- **IANA designation:** Defense Information Systems Agency +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/023-000-000-000--08--arin.md b/registry-ips/023-000-000-000--08--arin.md new file mode 100644 index 0000000..1408947 --- /dev/null +++ b/registry-ips/023-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 23.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **23.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `23.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-11 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/024-000-000-000--08--arin.md b/registry-ips/024-000-000-000--08--arin.md new file mode 100644 index 0000000..f47aec3 --- /dev/null +++ b/registry-ips/024-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 24.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **24.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `24.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2001-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/025-000-000-000--08--ripe-ncc.md b/registry-ips/025-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..350e3b4 --- /dev/null +++ b/registry-ips/025-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 25.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **25.0.0.0/8** to **Administered by RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `25.0.0.0/8` +- **IANA designation:** Administered by RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-01 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/026-000-000-000--08--arin.md b/registry-ips/026-000-000-000--08--arin.md new file mode 100644 index 0000000..51bade3 --- /dev/null +++ b/registry-ips/026-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 26.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **26.0.0.0/8** to **Defense Information Systems Agency** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `26.0.0.0/8` +- **IANA designation:** Defense Information Systems Agency +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/027-000-000-000--08--apnic.md b/registry-ips/027-000-000-000--08--apnic.md new file mode 100644 index 0000000..0f5b703 --- /dev/null +++ b/registry-ips/027-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 27.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **27.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `27.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/028-000-000-000--08--arin.md b/registry-ips/028-000-000-000--08--arin.md new file mode 100644 index 0000000..274f9f7 --- /dev/null +++ b/registry-ips/028-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 28.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **28.0.0.0/8** to **DSI-North** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `28.0.0.0/8` +- **IANA designation:** DSI-North +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1992-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/029-000-000-000--08--arin.md b/registry-ips/029-000-000-000--08--arin.md new file mode 100644 index 0000000..33d9dd5 --- /dev/null +++ b/registry-ips/029-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 29.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **29.0.0.0/8** to **Defense Information Systems Agency** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `29.0.0.0/8` +- **IANA designation:** Defense Information Systems Agency +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1991-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/030-000-000-000--08--arin.md b/registry-ips/030-000-000-000--08--arin.md new file mode 100644 index 0000000..c70f8a3 --- /dev/null +++ b/registry-ips/030-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 30.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **30.0.0.0/8** to **Defense Information Systems Agency** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `30.0.0.0/8` +- **IANA designation:** Defense Information Systems Agency +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1991-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/031-000-000-000--08--ripe-ncc.md b/registry-ips/031-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..9f9721a --- /dev/null +++ b/registry-ips/031-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 31.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **31.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `31.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/032-000-000-000--08--arin.md b/registry-ips/032-000-000-000--08--arin.md new file mode 100644 index 0000000..86df746 --- /dev/null +++ b/registry-ips/032-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 32.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **32.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `32.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/033-000-000-000--08--arin.md b/registry-ips/033-000-000-000--08--arin.md new file mode 100644 index 0000000..d7003f9 --- /dev/null +++ b/registry-ips/033-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 33.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **33.0.0.0/8** to **DLA Systems Automation Center** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `33.0.0.0/8` +- **IANA designation:** DLA Systems Automation Center +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1991-01 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/034-000-000-000--08--arin.md b/registry-ips/034-000-000-000--08--arin.md new file mode 100644 index 0000000..3801c87 --- /dev/null +++ b/registry-ips/034-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 34.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **34.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `34.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-03 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/035-000-000-000--08--arin.md b/registry-ips/035-000-000-000--08--arin.md new file mode 100644 index 0000000..3c39548 --- /dev/null +++ b/registry-ips/035-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 35.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **35.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `35.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-04 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/036-000-000-000--08--apnic.md b/registry-ips/036-000-000-000--08--apnic.md new file mode 100644 index 0000000..687f0cb --- /dev/null +++ b/registry-ips/036-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 36.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **36.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `36.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-10 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/037-000-000-000--08--ripe-ncc.md b/registry-ips/037-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..ef1c2f2 --- /dev/null +++ b/registry-ips/037-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 37.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **37.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `37.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-11 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/038-000-000-000--08--arin.md b/registry-ips/038-000-000-000--08--arin.md new file mode 100644 index 0000000..21280d7 --- /dev/null +++ b/registry-ips/038-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 38.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **38.0.0.0/8** to **PSINet, Inc.** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `38.0.0.0/8` +- **IANA designation:** PSINet, Inc. +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-09 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/039-000-000-000--08--apnic.md b/registry-ips/039-000-000-000--08--apnic.md new file mode 100644 index 0000000..8c9105e --- /dev/null +++ b/registry-ips/039-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 39.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **39.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `39.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2011-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/040-000-000-000--08--arin.md b/registry-ips/040-000-000-000--08--arin.md new file mode 100644 index 0000000..bc15ac0 --- /dev/null +++ b/registry-ips/040-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 40.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **40.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `40.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/041-000-000-000--08--afrinic.md b/registry-ips/041-000-000-000--08--afrinic.md new file mode 100644 index 0000000..d9de980 --- /dev/null +++ b/registry-ips/041-000-000-000--08--afrinic.md @@ -0,0 +1,28 @@ + +# 41.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **41.0.0.0/8** to **AFRINIC** and the RDAP authority maps to **afrinic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `41.0.0.0/8` +- **IANA designation:** AFRINIC +- **Registry suffix:** `afrinic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-04 +- **WHOIS authority:** whois.afrinic.net +- **RDAP authority:** https://rdap.afrinic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/042-000-000-000--08--apnic.md b/registry-ips/042-000-000-000--08--apnic.md new file mode 100644 index 0000000..5a5d250 --- /dev/null +++ b/registry-ips/042-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 42.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **42.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `42.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-10 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/043-000-000-000--08--apnic.md b/registry-ips/043-000-000-000--08--apnic.md new file mode 100644 index 0000000..3234a6d --- /dev/null +++ b/registry-ips/043-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 43.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **43.0.0.0/8** to **Administered by APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `43.0.0.0/8` +- **IANA designation:** Administered by APNIC +- **Registry suffix:** `apnic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1991-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/044-000-000-000--08--arin.md b/registry-ips/044-000-000-000--08--arin.md new file mode 100644 index 0000000..9206fae --- /dev/null +++ b/registry-ips/044-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 44.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **44.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `44.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1992-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/045-000-000-000--08--arin.md b/registry-ips/045-000-000-000--08--arin.md new file mode 100644 index 0000000..31a80df --- /dev/null +++ b/registry-ips/045-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 45.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **45.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `45.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-01 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/046-000-000-000--08--ripe-ncc.md b/registry-ips/046-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..0f3148c --- /dev/null +++ b/registry-ips/046-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 46.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **46.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `46.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2009-09 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/047-000-000-000--08--arin.md b/registry-ips/047-000-000-000--08--arin.md new file mode 100644 index 0000000..40fe290 --- /dev/null +++ b/registry-ips/047-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 47.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **47.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `47.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1991-01 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/048-000-000-000--08--arin.md b/registry-ips/048-000-000-000--08--arin.md new file mode 100644 index 0000000..98c2892 --- /dev/null +++ b/registry-ips/048-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 48.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **48.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `48.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/049-000-000-000--08--apnic.md b/registry-ips/049-000-000-000--08--apnic.md new file mode 100644 index 0000000..26f2e99 --- /dev/null +++ b/registry-ips/049-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 49.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **49.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `49.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-08 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/050-000-000-000--08--arin.md b/registry-ips/050-000-000-000--08--arin.md new file mode 100644 index 0000000..8db41f5 --- /dev/null +++ b/registry-ips/050-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 50.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **50.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `50.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-02 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/051-000-000-000--08--ripe-ncc.md b/registry-ips/051-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..68bfc4b --- /dev/null +++ b/registry-ips/051-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 51.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **51.0.0.0/8** to **Administered by RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `51.0.0.0/8` +- **IANA designation:** Administered by RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-08 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/052-000-000-000--08--arin.md b/registry-ips/052-000-000-000--08--arin.md new file mode 100644 index 0000000..e3fd907 --- /dev/null +++ b/registry-ips/052-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 52.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **52.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `52.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1991-12 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/053-000-000-000--08--ripe-ncc.md b/registry-ips/053-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..5b451d5 --- /dev/null +++ b/registry-ips/053-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 53.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **53.0.0.0/8** to **Daimler AG** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `53.0.0.0/8` +- **IANA designation:** Daimler AG +- **Registry suffix:** `ripe-ncc` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-10 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/054-000-000-000--08--arin.md b/registry-ips/054-000-000-000--08--arin.md new file mode 100644 index 0000000..fb6b2e4 --- /dev/null +++ b/registry-ips/054-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 54.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **54.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `54.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1992-03 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/055-000-000-000--08--arin.md b/registry-ips/055-000-000-000--08--arin.md new file mode 100644 index 0000000..57ad092 --- /dev/null +++ b/registry-ips/055-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 55.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **55.0.0.0/8** to **DoD Network Information Center** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `55.0.0.0/8` +- **IANA designation:** DoD Network Information Center +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-04 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/056-000-000-000--08--arin.md b/registry-ips/056-000-000-000--08--arin.md new file mode 100644 index 0000000..a02354a --- /dev/null +++ b/registry-ips/056-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 56.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **56.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `56.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1994-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/057-000-000-000--08--ripe-ncc.md b/registry-ips/057-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..7a6891a --- /dev/null +++ b/registry-ips/057-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 57.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **57.0.0.0/8** to **Administered by RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `57.0.0.0/8` +- **IANA designation:** Administered by RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** LEGACY +- **Allocation/record date:** 1995-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/058-000-000-000--08--apnic.md b/registry-ips/058-000-000-000--08--apnic.md new file mode 100644 index 0000000..97ca2c6 --- /dev/null +++ b/registry-ips/058-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 58.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **58.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `58.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-04 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/059-000-000-000--08--apnic.md b/registry-ips/059-000-000-000--08--apnic.md new file mode 100644 index 0000000..d79bfe6 --- /dev/null +++ b/registry-ips/059-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 59.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **59.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `59.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-04 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/060-000-000-000--08--apnic.md b/registry-ips/060-000-000-000--08--apnic.md new file mode 100644 index 0000000..3f7e3ac --- /dev/null +++ b/registry-ips/060-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 60.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **60.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `60.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2003-04 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/061-000-000-000--08--apnic.md b/registry-ips/061-000-000-000--08--apnic.md new file mode 100644 index 0000000..6c6fe13 --- /dev/null +++ b/registry-ips/061-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 61.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **61.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `61.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1997-04 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/062-000-000-000--08--ripe-ncc.md b/registry-ips/062-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..9e15fb4 --- /dev/null +++ b/registry-ips/062-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 62.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **62.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `62.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1997-04 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/063-000-000-000--08--arin.md b/registry-ips/063-000-000-000--08--arin.md new file mode 100644 index 0000000..aeb7465 --- /dev/null +++ b/registry-ips/063-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 63.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **63.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `63.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1997-04 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/064-000-000-000--08--arin.md b/registry-ips/064-000-000-000--08--arin.md new file mode 100644 index 0000000..ccf517b --- /dev/null +++ b/registry-ips/064-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 64.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **64.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `64.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1999-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/065-000-000-000--08--arin.md b/registry-ips/065-000-000-000--08--arin.md new file mode 100644 index 0000000..6356c77 --- /dev/null +++ b/registry-ips/065-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 65.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **65.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `65.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2000-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/066-000-000-000--08--arin.md b/registry-ips/066-000-000-000--08--arin.md new file mode 100644 index 0000000..a848a7e --- /dev/null +++ b/registry-ips/066-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 66.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **66.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `66.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2000-07 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/067-000-000-000--08--arin.md b/registry-ips/067-000-000-000--08--arin.md new file mode 100644 index 0000000..198499a --- /dev/null +++ b/registry-ips/067-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 67.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **67.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `67.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2001-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/068-000-000-000--08--arin.md b/registry-ips/068-000-000-000--08--arin.md new file mode 100644 index 0000000..68cdc59 --- /dev/null +++ b/registry-ips/068-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 68.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **68.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `68.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2001-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/069-000-000-000--08--arin.md b/registry-ips/069-000-000-000--08--arin.md new file mode 100644 index 0000000..c764da4 --- /dev/null +++ b/registry-ips/069-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 69.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **69.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `69.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2002-08 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/070-000-000-000--08--arin.md b/registry-ips/070-000-000-000--08--arin.md new file mode 100644 index 0000000..78893ce --- /dev/null +++ b/registry-ips/070-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 70.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **70.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `70.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-01 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/071-000-000-000--08--arin.md b/registry-ips/071-000-000-000--08--arin.md new file mode 100644 index 0000000..31d833a --- /dev/null +++ b/registry-ips/071-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 71.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **71.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `71.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-08 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/072-000-000-000--08--arin.md b/registry-ips/072-000-000-000--08--arin.md new file mode 100644 index 0000000..4efea84 --- /dev/null +++ b/registry-ips/072-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 72.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **72.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `72.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-08 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/073-000-000-000--08--arin.md b/registry-ips/073-000-000-000--08--arin.md new file mode 100644 index 0000000..5f1a68d --- /dev/null +++ b/registry-ips/073-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 73.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **73.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `73.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-03 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/074-000-000-000--08--arin.md b/registry-ips/074-000-000-000--08--arin.md new file mode 100644 index 0000000..e5a9dbe --- /dev/null +++ b/registry-ips/074-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 74.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **74.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `74.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/075-000-000-000--08--arin.md b/registry-ips/075-000-000-000--08--arin.md new file mode 100644 index 0000000..db0260e --- /dev/null +++ b/registry-ips/075-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 75.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **75.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `75.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/076-000-000-000--08--arin.md b/registry-ips/076-000-000-000--08--arin.md new file mode 100644 index 0000000..15dad45 --- /dev/null +++ b/registry-ips/076-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 76.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **76.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `76.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/077-000-000-000--08--ripe-ncc.md b/registry-ips/077-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..d3e3c8d --- /dev/null +++ b/registry-ips/077-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 77.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **77.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `77.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-08 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/078-000-000-000--08--ripe-ncc.md b/registry-ips/078-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..e785d52 --- /dev/null +++ b/registry-ips/078-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 78.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **78.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `78.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-08 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/079-000-000-000--08--ripe-ncc.md b/registry-ips/079-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..da0b5d1 --- /dev/null +++ b/registry-ips/079-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 79.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **79.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `79.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-08 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/080-000-000-000--08--ripe-ncc.md b/registry-ips/080-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..619c3a7 --- /dev/null +++ b/registry-ips/080-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 80.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **80.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `80.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2001-04 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/081-000-000-000--08--ripe-ncc.md b/registry-ips/081-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..76eb0ae --- /dev/null +++ b/registry-ips/081-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 81.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **81.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `81.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2001-04 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/082-000-000-000--08--ripe-ncc.md b/registry-ips/082-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..233af12 --- /dev/null +++ b/registry-ips/082-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 82.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **82.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `82.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2002-11 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/083-000-000-000--08--ripe-ncc.md b/registry-ips/083-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..310da2c --- /dev/null +++ b/registry-ips/083-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 83.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **83.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `83.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2003-11 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/084-000-000-000--08--ripe-ncc.md b/registry-ips/084-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..52b2073 --- /dev/null +++ b/registry-ips/084-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 84.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **84.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `84.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2003-11 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/085-000-000-000--08--ripe-ncc.md b/registry-ips/085-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..d418da6 --- /dev/null +++ b/registry-ips/085-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 85.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **85.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `85.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-04 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/086-000-000-000--08--ripe-ncc.md b/registry-ips/086-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..5708dcb --- /dev/null +++ b/registry-ips/086-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 86.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **86.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `86.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-04 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/087-000-000-000--08--ripe-ncc.md b/registry-ips/087-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..ba1ddec --- /dev/null +++ b/registry-ips/087-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 87.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **87.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `87.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-04 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/088-000-000-000--08--ripe-ncc.md b/registry-ips/088-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..710e360 --- /dev/null +++ b/registry-ips/088-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 88.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **88.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `88.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2004-04 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/089-000-000-000--08--ripe-ncc.md b/registry-ips/089-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..5d9ac6d --- /dev/null +++ b/registry-ips/089-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 89.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **89.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `89.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-06 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/090-000-000-000--08--ripe-ncc.md b/registry-ips/090-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..ad99f49 --- /dev/null +++ b/registry-ips/090-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 90.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **90.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `90.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-06 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/091-000-000-000--08--ripe-ncc.md b/registry-ips/091-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..ee285f6 --- /dev/null +++ b/registry-ips/091-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 91.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **91.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `91.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-06 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/092-000-000-000--08--ripe-ncc.md b/registry-ips/092-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..8a2cbb0 --- /dev/null +++ b/registry-ips/092-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 92.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **92.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `92.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-03 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/093-000-000-000--08--ripe-ncc.md b/registry-ips/093-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..447849b --- /dev/null +++ b/registry-ips/093-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 93.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **93.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `93.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-03 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/094-000-000-000--08--ripe-ncc.md b/registry-ips/094-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..663a458 --- /dev/null +++ b/registry-ips/094-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 94.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **94.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `94.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-07 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/095-000-000-000--08--ripe-ncc.md b/registry-ips/095-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..f9ccd89 --- /dev/null +++ b/registry-ips/095-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 95.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **95.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `95.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-07 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/096-000-000-000--08--arin.md b/registry-ips/096-000-000-000--08--arin.md new file mode 100644 index 0000000..57d1cb2 --- /dev/null +++ b/registry-ips/096-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 96.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **96.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `96.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-10 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/097-000-000-000--08--arin.md b/registry-ips/097-000-000-000--08--arin.md new file mode 100644 index 0000000..2bd3daf --- /dev/null +++ b/registry-ips/097-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 97.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **97.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `97.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-10 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/098-000-000-000--08--arin.md b/registry-ips/098-000-000-000--08--arin.md new file mode 100644 index 0000000..e852d09 --- /dev/null +++ b/registry-ips/098-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 98.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **98.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `98.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-10 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/099-000-000-000--08--arin.md b/registry-ips/099-000-000-000--08--arin.md new file mode 100644 index 0000000..5ff4b63 --- /dev/null +++ b/registry-ips/099-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 99.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **99.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `99.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-10 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/100-000-000-000--08--arin.md b/registry-ips/100-000-000-000--08--arin.md new file mode 100644 index 0000000..6351286 --- /dev/null +++ b/registry-ips/100-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 100.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **100.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `100.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-11 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** [6] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/100-064-000-000--10--iana-special.md b/registry-ips/100-064-000-000--10--iana-special.md new file mode 100644 index 0000000..b56fb4b --- /dev/null +++ b/registry-ips/100-064-000-000--10--iana-special.md @@ -0,0 +1,28 @@ + +# 100.64.0.0/10 — Shared Address Space + +## Who is this IP range? + +IANA identifies **100.64.0.0/10** as **Shared Address Space** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `100.64.0.0/10` +- **Name:** Shared Address Space +- **RFC/reference:** [RFC6598] +- **Allocation date:** 2012-04 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/101-000-000-000--08--apnic.md b/registry-ips/101-000-000-000--08--apnic.md new file mode 100644 index 0000000..3585b3a --- /dev/null +++ b/registry-ips/101-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 101.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **101.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `101.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-08 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/102-000-000-000--08--afrinic.md b/registry-ips/102-000-000-000--08--afrinic.md new file mode 100644 index 0000000..24611c6 --- /dev/null +++ b/registry-ips/102-000-000-000--08--afrinic.md @@ -0,0 +1,28 @@ + +# 102.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **102.0.0.0/8** to **AFRINIC** and the RDAP authority maps to **afrinic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `102.0.0.0/8` +- **IANA designation:** AFRINIC +- **Registry suffix:** `afrinic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2011-02 +- **WHOIS authority:** whois.afrinic.net +- **RDAP authority:** https://rdap.afrinic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/103-000-000-000--08--apnic.md b/registry-ips/103-000-000-000--08--apnic.md new file mode 100644 index 0000000..acfe2a5 --- /dev/null +++ b/registry-ips/103-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 103.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **103.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `103.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2011-02 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/104-000-000-000--08--arin.md b/registry-ips/104-000-000-000--08--arin.md new file mode 100644 index 0000000..fbbf9bf --- /dev/null +++ b/registry-ips/104-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 104.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **104.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `104.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2011-02 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/105-000-000-000--08--afrinic.md b/registry-ips/105-000-000-000--08--afrinic.md new file mode 100644 index 0000000..ce3042b --- /dev/null +++ b/registry-ips/105-000-000-000--08--afrinic.md @@ -0,0 +1,28 @@ + +# 105.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **105.0.0.0/8** to **AFRINIC** and the RDAP authority maps to **afrinic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `105.0.0.0/8` +- **IANA designation:** AFRINIC +- **Registry suffix:** `afrinic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-11 +- **WHOIS authority:** whois.afrinic.net +- **RDAP authority:** https://rdap.afrinic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/106-000-000-000--08--apnic.md b/registry-ips/106-000-000-000--08--apnic.md new file mode 100644 index 0000000..30a2204 --- /dev/null +++ b/registry-ips/106-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 106.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **106.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `106.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2011-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/107-000-000-000--08--arin.md b/registry-ips/107-000-000-000--08--arin.md new file mode 100644 index 0000000..5121713 --- /dev/null +++ b/registry-ips/107-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 107.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **107.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `107.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-02 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/108-000-000-000--08--arin.md b/registry-ips/108-000-000-000--08--arin.md new file mode 100644 index 0000000..b93a002 --- /dev/null +++ b/registry-ips/108-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 108.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **108.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `108.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-12 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/109-000-000-000--08--ripe-ncc.md b/registry-ips/109-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..f8af697 --- /dev/null +++ b/registry-ips/109-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 109.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **109.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `109.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2009-01 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/110-000-000-000--08--apnic.md b/registry-ips/110-000-000-000--08--apnic.md new file mode 100644 index 0000000..2fc1472 --- /dev/null +++ b/registry-ips/110-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 110.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **110.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `110.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-11 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/111-000-000-000--08--apnic.md b/registry-ips/111-000-000-000--08--apnic.md new file mode 100644 index 0000000..7e799d8 --- /dev/null +++ b/registry-ips/111-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 111.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **111.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `111.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-11 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/112-000-000-000--08--apnic.md b/registry-ips/112-000-000-000--08--apnic.md new file mode 100644 index 0000000..15700ac --- /dev/null +++ b/registry-ips/112-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 112.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **112.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `112.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-05 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/113-000-000-000--08--apnic.md b/registry-ips/113-000-000-000--08--apnic.md new file mode 100644 index 0000000..aace09a --- /dev/null +++ b/registry-ips/113-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 113.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **113.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `113.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-05 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/114-000-000-000--08--apnic.md b/registry-ips/114-000-000-000--08--apnic.md new file mode 100644 index 0000000..724c43a --- /dev/null +++ b/registry-ips/114-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 114.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **114.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `114.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-10 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/115-000-000-000--08--apnic.md b/registry-ips/115-000-000-000--08--apnic.md new file mode 100644 index 0000000..92a951d --- /dev/null +++ b/registry-ips/115-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 115.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **115.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `115.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-10 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/116-000-000-000--08--apnic.md b/registry-ips/116-000-000-000--08--apnic.md new file mode 100644 index 0000000..9b02981 --- /dev/null +++ b/registry-ips/116-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 116.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **116.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `116.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/117-000-000-000--08--apnic.md b/registry-ips/117-000-000-000--08--apnic.md new file mode 100644 index 0000000..e76b93e --- /dev/null +++ b/registry-ips/117-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 117.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **117.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `117.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/118-000-000-000--08--apnic.md b/registry-ips/118-000-000-000--08--apnic.md new file mode 100644 index 0000000..2e60353 --- /dev/null +++ b/registry-ips/118-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 118.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **118.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `118.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/119-000-000-000--08--apnic.md b/registry-ips/119-000-000-000--08--apnic.md new file mode 100644 index 0000000..442105c --- /dev/null +++ b/registry-ips/119-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 119.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **119.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `119.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/120-000-000-000--08--apnic.md b/registry-ips/120-000-000-000--08--apnic.md new file mode 100644 index 0000000..9057914 --- /dev/null +++ b/registry-ips/120-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 120.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **120.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `120.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/121-000-000-000--08--apnic.md b/registry-ips/121-000-000-000--08--apnic.md new file mode 100644 index 0000000..2f53f88 --- /dev/null +++ b/registry-ips/121-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 121.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **121.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `121.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/122-000-000-000--08--apnic.md b/registry-ips/122-000-000-000--08--apnic.md new file mode 100644 index 0000000..e15ef9e --- /dev/null +++ b/registry-ips/122-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 122.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **122.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `122.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/123-000-000-000--08--apnic.md b/registry-ips/123-000-000-000--08--apnic.md new file mode 100644 index 0000000..35c9d4b --- /dev/null +++ b/registry-ips/123-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 123.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **123.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `123.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2006-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/124-000-000-000--08--apnic.md b/registry-ips/124-000-000-000--08--apnic.md new file mode 100644 index 0000000..cea2c8e --- /dev/null +++ b/registry-ips/124-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 124.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **124.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `124.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/125-000-000-000--08--apnic.md b/registry-ips/125-000-000-000--08--apnic.md new file mode 100644 index 0000000..7e44ead --- /dev/null +++ b/registry-ips/125-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 125.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **125.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `125.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/126-000-000-000--08--apnic.md b/registry-ips/126-000-000-000--08--apnic.md new file mode 100644 index 0000000..e661ed1 --- /dev/null +++ b/registry-ips/126-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 126.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **126.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `126.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2005-01 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/127-000-000-000--08--iana-special.md b/registry-ips/127-000-000-000--08--iana-special.md new file mode 100644 index 0000000..e55acd7 --- /dev/null +++ b/registry-ips/127-000-000-000--08--iana-special.md @@ -0,0 +1,28 @@ + +# 127.0.0.0/8 — Loopback + +## Who is this IP range? + +IANA identifies **127.0.0.0/8** as **Loopback** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `127.0.0.0/8` +- **Name:** Loopback +- **RFC/reference:** [RFC1122], Section 3.2.1.3 +- **Allocation date:** 1981-09 +- **Termination date:** N/A +- **Valid as source:** False [1] +- **Valid as destination:** False [1] +- **Forwardable:** False [1] +- **Globally reachable:** False [1] +- **Reserved by protocol:** True +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/127-000-000-000--08--iana.md b/registry-ips/127-000-000-000--08--iana.md new file mode 100644 index 0000000..450e47d --- /dev/null +++ b/registry-ips/127-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 127.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **127.0.0.0/8** as **IANA - Loopback** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `127.0.0.0/8` +- **IANA designation:** IANA - Loopback +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [7] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/128-000-000-000--08--arin.md b/registry-ips/128-000-000-000--08--arin.md new file mode 100644 index 0000000..fea73d4 --- /dev/null +++ b/registry-ips/128-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 128.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **128.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `128.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/129-000-000-000--08--arin.md b/registry-ips/129-000-000-000--08--arin.md new file mode 100644 index 0000000..e1285b4 --- /dev/null +++ b/registry-ips/129-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 129.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **129.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `129.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/130-000-000-000--08--arin.md b/registry-ips/130-000-000-000--08--arin.md new file mode 100644 index 0000000..b3acf24 --- /dev/null +++ b/registry-ips/130-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 130.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **130.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `130.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/131-000-000-000--08--arin.md b/registry-ips/131-000-000-000--08--arin.md new file mode 100644 index 0000000..8b8f870 --- /dev/null +++ b/registry-ips/131-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 131.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **131.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `131.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/132-000-000-000--08--arin.md b/registry-ips/132-000-000-000--08--arin.md new file mode 100644 index 0000000..de1578b --- /dev/null +++ b/registry-ips/132-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 132.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **132.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `132.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/133-000-000-000--08--apnic.md b/registry-ips/133-000-000-000--08--apnic.md new file mode 100644 index 0000000..41e46b4 --- /dev/null +++ b/registry-ips/133-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 133.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **133.0.0.0/8** to **Administered by APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `133.0.0.0/8` +- **IANA designation:** Administered by APNIC +- **Registry suffix:** `apnic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1997-03 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/134-000-000-000--08--arin.md b/registry-ips/134-000-000-000--08--arin.md new file mode 100644 index 0000000..b24dfde --- /dev/null +++ b/registry-ips/134-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 134.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **134.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `134.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/135-000-000-000--08--arin.md b/registry-ips/135-000-000-000--08--arin.md new file mode 100644 index 0000000..0a2e3c9 --- /dev/null +++ b/registry-ips/135-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 135.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **135.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `135.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/136-000-000-000--08--arin.md b/registry-ips/136-000-000-000--08--arin.md new file mode 100644 index 0000000..38968b2 --- /dev/null +++ b/registry-ips/136-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 136.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **136.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `136.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/137-000-000-000--08--arin.md b/registry-ips/137-000-000-000--08--arin.md new file mode 100644 index 0000000..37f2da3 --- /dev/null +++ b/registry-ips/137-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 137.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **137.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `137.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/138-000-000-000--08--arin.md b/registry-ips/138-000-000-000--08--arin.md new file mode 100644 index 0000000..983fb88 --- /dev/null +++ b/registry-ips/138-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 138.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **138.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `138.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/139-000-000-000--08--arin.md b/registry-ips/139-000-000-000--08--arin.md new file mode 100644 index 0000000..bcaa536 --- /dev/null +++ b/registry-ips/139-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 139.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **139.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `139.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/140-000-000-000--08--arin.md b/registry-ips/140-000-000-000--08--arin.md new file mode 100644 index 0000000..ae794e6 --- /dev/null +++ b/registry-ips/140-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 140.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **140.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `140.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/141-000-000-000--08--ripe-ncc.md b/registry-ips/141-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..8b6b91a --- /dev/null +++ b/registry-ips/141-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 141.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **141.0.0.0/8** to **Administered by RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `141.0.0.0/8` +- **IANA designation:** Administered by RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/142-000-000-000--08--arin.md b/registry-ips/142-000-000-000--08--arin.md new file mode 100644 index 0000000..02fcb65 --- /dev/null +++ b/registry-ips/142-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 142.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **142.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `142.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/143-000-000-000--08--arin.md b/registry-ips/143-000-000-000--08--arin.md new file mode 100644 index 0000000..00d9662 --- /dev/null +++ b/registry-ips/143-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 143.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **143.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `143.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/144-000-000-000--08--arin.md b/registry-ips/144-000-000-000--08--arin.md new file mode 100644 index 0000000..a4fed63 --- /dev/null +++ b/registry-ips/144-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 144.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **144.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `144.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/145-000-000-000--08--ripe-ncc.md b/registry-ips/145-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..e95c278 --- /dev/null +++ b/registry-ips/145-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 145.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **145.0.0.0/8** to **Administered by RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `145.0.0.0/8` +- **IANA designation:** Administered by RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/146-000-000-000--08--arin.md b/registry-ips/146-000-000-000--08--arin.md new file mode 100644 index 0000000..4491a82 --- /dev/null +++ b/registry-ips/146-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 146.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **146.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `146.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/147-000-000-000--08--arin.md b/registry-ips/147-000-000-000--08--arin.md new file mode 100644 index 0000000..780fbbf --- /dev/null +++ b/registry-ips/147-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 147.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **147.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `147.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/148-000-000-000--08--arin.md b/registry-ips/148-000-000-000--08--arin.md new file mode 100644 index 0000000..b0df8b9 --- /dev/null +++ b/registry-ips/148-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 148.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **148.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `148.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/149-000-000-000--08--arin.md b/registry-ips/149-000-000-000--08--arin.md new file mode 100644 index 0000000..5ae2061 --- /dev/null +++ b/registry-ips/149-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 149.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **149.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `149.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/150-000-000-000--08--apnic.md b/registry-ips/150-000-000-000--08--apnic.md new file mode 100644 index 0000000..79226de --- /dev/null +++ b/registry-ips/150-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 150.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **150.0.0.0/8** to **Administered by APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `150.0.0.0/8` +- **IANA designation:** Administered by APNIC +- **Registry suffix:** `apnic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/151-000-000-000--08--ripe-ncc.md b/registry-ips/151-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..29ff5db --- /dev/null +++ b/registry-ips/151-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 151.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **151.0.0.0/8** to **Administered by RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `151.0.0.0/8` +- **IANA designation:** Administered by RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/152-000-000-000--08--arin.md b/registry-ips/152-000-000-000--08--arin.md new file mode 100644 index 0000000..a3b1924 --- /dev/null +++ b/registry-ips/152-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 152.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **152.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `152.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/153-000-000-000--08--apnic.md b/registry-ips/153-000-000-000--08--apnic.md new file mode 100644 index 0000000..b5d3a25 --- /dev/null +++ b/registry-ips/153-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 153.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **153.0.0.0/8** to **Administered by APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `153.0.0.0/8` +- **IANA designation:** Administered by APNIC +- **Registry suffix:** `apnic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/154-000-000-000--08--afrinic.md b/registry-ips/154-000-000-000--08--afrinic.md new file mode 100644 index 0000000..bd86093 --- /dev/null +++ b/registry-ips/154-000-000-000--08--afrinic.md @@ -0,0 +1,28 @@ + +# 154.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **154.0.0.0/8** to **Administered by AFRINIC** and the RDAP authority maps to **afrinic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `154.0.0.0/8` +- **IANA designation:** Administered by AFRINIC +- **Registry suffix:** `afrinic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.afrinic.net +- **RDAP authority:** https://rdap.afrinic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/155-000-000-000--08--arin.md b/registry-ips/155-000-000-000--08--arin.md new file mode 100644 index 0000000..71e2a05 --- /dev/null +++ b/registry-ips/155-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 155.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **155.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `155.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/156-000-000-000--08--arin.md b/registry-ips/156-000-000-000--08--arin.md new file mode 100644 index 0000000..bbd1db1 --- /dev/null +++ b/registry-ips/156-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 156.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **156.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `156.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/157-000-000-000--08--arin.md b/registry-ips/157-000-000-000--08--arin.md new file mode 100644 index 0000000..a142513 --- /dev/null +++ b/registry-ips/157-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 157.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **157.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `157.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/158-000-000-000--08--arin.md b/registry-ips/158-000-000-000--08--arin.md new file mode 100644 index 0000000..08fa2fa --- /dev/null +++ b/registry-ips/158-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 158.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **158.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `158.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/159-000-000-000--08--arin.md b/registry-ips/159-000-000-000--08--arin.md new file mode 100644 index 0000000..ceff177 --- /dev/null +++ b/registry-ips/159-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 159.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **159.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `159.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/160-000-000-000--08--arin.md b/registry-ips/160-000-000-000--08--arin.md new file mode 100644 index 0000000..0da6a46 --- /dev/null +++ b/registry-ips/160-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 160.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **160.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `160.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/161-000-000-000--08--arin.md b/registry-ips/161-000-000-000--08--arin.md new file mode 100644 index 0000000..6c796b1 --- /dev/null +++ b/registry-ips/161-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 161.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **161.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `161.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/162-000-000-000--08--arin.md b/registry-ips/162-000-000-000--08--arin.md new file mode 100644 index 0000000..ea55015 --- /dev/null +++ b/registry-ips/162-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 162.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **162.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `162.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/163-000-000-000--08--apnic.md b/registry-ips/163-000-000-000--08--apnic.md new file mode 100644 index 0000000..ee61c81 --- /dev/null +++ b/registry-ips/163-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 163.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **163.0.0.0/8** to **Administered by APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `163.0.0.0/8` +- **IANA designation:** Administered by APNIC +- **Registry suffix:** `apnic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/164-000-000-000--08--arin.md b/registry-ips/164-000-000-000--08--arin.md new file mode 100644 index 0000000..54d4c74 --- /dev/null +++ b/registry-ips/164-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 164.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **164.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `164.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/165-000-000-000--08--arin.md b/registry-ips/165-000-000-000--08--arin.md new file mode 100644 index 0000000..209742b --- /dev/null +++ b/registry-ips/165-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 165.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **165.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `165.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/166-000-000-000--08--arin.md b/registry-ips/166-000-000-000--08--arin.md new file mode 100644 index 0000000..108f6be --- /dev/null +++ b/registry-ips/166-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 166.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **166.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `166.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/167-000-000-000--08--arin.md b/registry-ips/167-000-000-000--08--arin.md new file mode 100644 index 0000000..0539c61 --- /dev/null +++ b/registry-ips/167-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 167.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **167.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `167.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/168-000-000-000--08--arin.md b/registry-ips/168-000-000-000--08--arin.md new file mode 100644 index 0000000..c10868d --- /dev/null +++ b/registry-ips/168-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 168.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **168.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `168.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/169-000-000-000--08--arin.md b/registry-ips/169-000-000-000--08--arin.md new file mode 100644 index 0000000..b416a47 --- /dev/null +++ b/registry-ips/169-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 169.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **169.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `169.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** [8] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/169-254-000-000--16--iana-special.md b/registry-ips/169-254-000-000--16--iana-special.md new file mode 100644 index 0000000..f79a7e8 --- /dev/null +++ b/registry-ips/169-254-000-000--16--iana-special.md @@ -0,0 +1,28 @@ + +# 169.254.0.0/16 — Link Local + +## Who is this IP range? + +IANA identifies **169.254.0.0/16** as **Link Local** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `169.254.0.0/16` +- **Name:** Link Local +- **RFC/reference:** [RFC3927] +- **Allocation date:** 2005-05 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** True +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/170-000-000-000--08--arin.md b/registry-ips/170-000-000-000--08--arin.md new file mode 100644 index 0000000..48a4e2f --- /dev/null +++ b/registry-ips/170-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 170.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **170.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `170.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/171-000-000-000--08--apnic.md b/registry-ips/171-000-000-000--08--apnic.md new file mode 100644 index 0000000..18ffc5c --- /dev/null +++ b/registry-ips/171-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 171.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **171.0.0.0/8** to **Administered by APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `171.0.0.0/8` +- **IANA designation:** Administered by APNIC +- **Registry suffix:** `apnic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/172-000-000-000--08--arin.md b/registry-ips/172-000-000-000--08--arin.md new file mode 100644 index 0000000..21b4ebe --- /dev/null +++ b/registry-ips/172-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 172.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **172.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `172.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** [9] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/172-016-000-000--12--iana-special.md b/registry-ips/172-016-000-000--12--iana-special.md new file mode 100644 index 0000000..f84a326 --- /dev/null +++ b/registry-ips/172-016-000-000--12--iana-special.md @@ -0,0 +1,28 @@ + +# 172.16.0.0/12 — Private-Use + +## Who is this IP range? + +IANA identifies **172.16.0.0/12** as **Private-Use** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `172.16.0.0/12` +- **Name:** Private-Use +- **RFC/reference:** [RFC1918] +- **Allocation date:** 1996-02 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/173-000-000-000--08--arin.md b/registry-ips/173-000-000-000--08--arin.md new file mode 100644 index 0000000..c0b3b22 --- /dev/null +++ b/registry-ips/173-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 173.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **173.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `173.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-02 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/174-000-000-000--08--arin.md b/registry-ips/174-000-000-000--08--arin.md new file mode 100644 index 0000000..485af12 --- /dev/null +++ b/registry-ips/174-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 174.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **174.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `174.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-02 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/175-000-000-000--08--apnic.md b/registry-ips/175-000-000-000--08--apnic.md new file mode 100644 index 0000000..4c3309e --- /dev/null +++ b/registry-ips/175-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 175.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **175.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `175.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2009-08 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/176-000-000-000--08--ripe-ncc.md b/registry-ips/176-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..2be64af --- /dev/null +++ b/registry-ips/176-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 176.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **176.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `176.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/177-000-000-000--08--lacnic.md b/registry-ips/177-000-000-000--08--lacnic.md new file mode 100644 index 0000000..cfea540 --- /dev/null +++ b/registry-ips/177-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 177.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **177.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `177.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-06 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/178-000-000-000--08--ripe-ncc.md b/registry-ips/178-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..7382b8f --- /dev/null +++ b/registry-ips/178-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 178.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **178.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `178.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2009-01 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/179-000-000-000--08--lacnic.md b/registry-ips/179-000-000-000--08--lacnic.md new file mode 100644 index 0000000..ee1032a --- /dev/null +++ b/registry-ips/179-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 179.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **179.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `179.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2011-02 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/180-000-000-000--08--apnic.md b/registry-ips/180-000-000-000--08--apnic.md new file mode 100644 index 0000000..f715e59 --- /dev/null +++ b/registry-ips/180-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 180.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **180.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `180.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2009-04 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/181-000-000-000--08--lacnic.md b/registry-ips/181-000-000-000--08--lacnic.md new file mode 100644 index 0000000..6e25806 --- /dev/null +++ b/registry-ips/181-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 181.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **181.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `181.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-06 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/182-000-000-000--08--apnic.md b/registry-ips/182-000-000-000--08--apnic.md new file mode 100644 index 0000000..be0c715 --- /dev/null +++ b/registry-ips/182-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 182.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **182.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `182.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2009-08 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/183-000-000-000--08--apnic.md b/registry-ips/183-000-000-000--08--apnic.md new file mode 100644 index 0000000..a3ac9d3 --- /dev/null +++ b/registry-ips/183-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 183.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **183.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `183.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2009-04 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/184-000-000-000--08--arin.md b/registry-ips/184-000-000-000--08--arin.md new file mode 100644 index 0000000..6495fbf --- /dev/null +++ b/registry-ips/184-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 184.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **184.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `184.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-12 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/185-000-000-000--08--ripe-ncc.md b/registry-ips/185-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..5c5e203 --- /dev/null +++ b/registry-ips/185-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 185.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **185.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `185.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2011-02 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/186-000-000-000--08--lacnic.md b/registry-ips/186-000-000-000--08--lacnic.md new file mode 100644 index 0000000..cf62132 --- /dev/null +++ b/registry-ips/186-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 186.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **186.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `186.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-09 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/187-000-000-000--08--lacnic.md b/registry-ips/187-000-000-000--08--lacnic.md new file mode 100644 index 0000000..a1fda4f --- /dev/null +++ b/registry-ips/187-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 187.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **187.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `187.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2007-09 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/188-000-000-000--08--ripe-ncc.md b/registry-ips/188-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..946c0d2 --- /dev/null +++ b/registry-ips/188-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 188.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **188.0.0.0/8** to **Administered by RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `188.0.0.0/8` +- **IANA designation:** Administered by RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/189-000-000-000--08--lacnic.md b/registry-ips/189-000-000-000--08--lacnic.md new file mode 100644 index 0000000..c0fa6e9 --- /dev/null +++ b/registry-ips/189-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 189.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **189.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `189.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1995-06 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/190-000-000-000--08--lacnic.md b/registry-ips/190-000-000-000--08--lacnic.md new file mode 100644 index 0000000..8937b54 --- /dev/null +++ b/registry-ips/190-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 190.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **190.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `190.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1995-06 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/191-000-000-000--08--lacnic.md b/registry-ips/191-000-000-000--08--lacnic.md new file mode 100644 index 0000000..50e8fb3 --- /dev/null +++ b/registry-ips/191-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 191.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **191.0.0.0/8** to **Administered by LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `191.0.0.0/8` +- **IANA designation:** Administered by LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-000-000--08--arin.md b/registry-ips/192-000-000-000--08--arin.md new file mode 100644 index 0000000..534d871 --- /dev/null +++ b/registry-ips/192-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 192.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **192.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `192.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** [10][11] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-000-000--24--iana-special.md b/registry-ips/192-000-000-000--24--iana-special.md new file mode 100644 index 0000000..2e7e341 --- /dev/null +++ b/registry-ips/192-000-000-000--24--iana-special.md @@ -0,0 +1,28 @@ + +# 192.0.0.0/24 — IETF Protocol Assignments + +## Who is this IP range? + +IANA identifies **192.0.0.0/24** as **IETF Protocol Assignments** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.0.0.0/24` +- **Name:** IETF Protocol Assignments +- **RFC/reference:** [RFC6890], Section 2.1 +- **Allocation date:** 2010-01 +- **Termination date:** N/A +- **Valid as source:** False +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-000-000--29--iana-special.md b/registry-ips/192-000-000-000--29--iana-special.md new file mode 100644 index 0000000..6cca2c7 --- /dev/null +++ b/registry-ips/192-000-000-000--29--iana-special.md @@ -0,0 +1,28 @@ + +# 192.0.0.0/29 — IPv4 Service Continuity Prefix + +## Who is this IP range? + +IANA identifies **192.0.0.0/29** as **IPv4 Service Continuity Prefix** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.0.0.0/29` +- **Name:** IPv4 Service Continuity Prefix +- **RFC/reference:** [RFC7335] +- **Allocation date:** 2011-06 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-000-008--32--iana-special.md b/registry-ips/192-000-000-008--32--iana-special.md new file mode 100644 index 0000000..3972fb7 --- /dev/null +++ b/registry-ips/192-000-000-008--32--iana-special.md @@ -0,0 +1,28 @@ + +# 192.0.0.8/32 — IPv4 dummy address + +## Who is this IP range? + +IANA identifies **192.0.0.8/32** as **IPv4 dummy address** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.0.0.8/32` +- **Name:** IPv4 dummy address +- **RFC/reference:** [RFC7600] +- **Allocation date:** 2015-03 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-000-009--32--iana-special.md b/registry-ips/192-000-000-009--32--iana-special.md new file mode 100644 index 0000000..956b89f --- /dev/null +++ b/registry-ips/192-000-000-009--32--iana-special.md @@ -0,0 +1,28 @@ + +# 192.0.0.9/32 — Port Control Protocol Anycast + +## Who is this IP range? + +IANA identifies **192.0.0.9/32** as **Port Control Protocol Anycast** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.0.0.9/32` +- **Name:** Port Control Protocol Anycast +- **RFC/reference:** [RFC7723] +- **Allocation date:** 2015-10 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** True +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-000-010--32--iana-special.md b/registry-ips/192-000-000-010--32--iana-special.md new file mode 100644 index 0000000..09882ab --- /dev/null +++ b/registry-ips/192-000-000-010--32--iana-special.md @@ -0,0 +1,28 @@ + +# 192.0.0.10/32 — Traversal Using Relays around NAT Anycast + +## Who is this IP range? + +IANA identifies **192.0.0.10/32** as **Traversal Using Relays around NAT Anycast** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.0.0.10/32` +- **Name:** Traversal Using Relays around NAT Anycast +- **RFC/reference:** [RFC8155] +- **Allocation date:** 2017-02 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** True +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-000-170--32--iana-special.md b/registry-ips/192-000-000-170--32--iana-special.md new file mode 100644 index 0000000..c5a20a6 --- /dev/null +++ b/registry-ips/192-000-000-170--32--iana-special.md @@ -0,0 +1,28 @@ + +# 192.0.0.170/32 — NAT64/DNS64 Discovery + +## Who is this IP range? + +IANA identifies **192.0.0.170/32** as **NAT64/DNS64 Discovery** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.0.0.170/32` +- **Name:** NAT64/DNS64 Discovery +- **RFC/reference:** [RFC8880][RFC7050], Section 2.2 +- **Allocation date:** 2013-02 +- **Termination date:** N/A +- **Valid as source:** False +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** True +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-000-171--32--iana-special.md b/registry-ips/192-000-000-171--32--iana-special.md new file mode 100644 index 0000000..f1aa4da --- /dev/null +++ b/registry-ips/192-000-000-171--32--iana-special.md @@ -0,0 +1,28 @@ + +# 192.0.0.171/32 — NAT64/DNS64 Discovery + +## Who is this IP range? + +IANA identifies **192.0.0.171/32** as **NAT64/DNS64 Discovery** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.0.0.171/32` +- **Name:** NAT64/DNS64 Discovery +- **RFC/reference:** [RFC8880][RFC7050], Section 2.2 +- **Allocation date:** 2013-02 +- **Termination date:** N/A +- **Valid as source:** False +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** True +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-000-002-000--24--iana-special.md b/registry-ips/192-000-002-000--24--iana-special.md new file mode 100644 index 0000000..14653b4 --- /dev/null +++ b/registry-ips/192-000-002-000--24--iana-special.md @@ -0,0 +1,28 @@ + +# 192.0.2.0/24 — Documentation (TEST-NET-1) + +## Who is this IP range? + +IANA identifies **192.0.2.0/24** as **Documentation (TEST-NET-1)** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.0.2.0/24` +- **Name:** Documentation (TEST-NET-1) +- **RFC/reference:** [RFC5737] +- **Allocation date:** 2010-01 +- **Termination date:** N/A +- **Valid as source:** False +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-031-196-000--24--iana-special.md b/registry-ips/192-031-196-000--24--iana-special.md new file mode 100644 index 0000000..bb056e0 --- /dev/null +++ b/registry-ips/192-031-196-000--24--iana-special.md @@ -0,0 +1,28 @@ + +# 192.31.196.0/24 — AS112-v4 + +## Who is this IP range? + +IANA identifies **192.31.196.0/24** as **AS112-v4** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.31.196.0/24` +- **Name:** AS112-v4 +- **RFC/reference:** [RFC7535] +- **Allocation date:** 2014-12 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** True +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-052-193-000--24--iana-special.md b/registry-ips/192-052-193-000--24--iana-special.md new file mode 100644 index 0000000..8084e00 --- /dev/null +++ b/registry-ips/192-052-193-000--24--iana-special.md @@ -0,0 +1,28 @@ + +# 192.52.193.0/24 — AMT + +## Who is this IP range? + +IANA identifies **192.52.193.0/24** as **AMT** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.52.193.0/24` +- **Name:** AMT +- **RFC/reference:** [RFC7450] +- **Allocation date:** 2014-12 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** True +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-088-099-000--24--iana-special.md b/registry-ips/192-088-099-000--24--iana-special.md new file mode 100644 index 0000000..7e19070 --- /dev/null +++ b/registry-ips/192-088-099-000--24--iana-special.md @@ -0,0 +1,28 @@ + +# 192.88.99.0/24 — Deprecated (6to4 Relay Anycast) + +## Who is this IP range? + +IANA identifies **192.88.99.0/24** as **Deprecated (6to4 Relay Anycast)** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.88.99.0/24` +- **Name:** Deprecated (6to4 Relay Anycast) +- **RFC/reference:** [RFC7526] +- **Allocation date:** 2001-06 +- **Termination date:** 2015-03 +- **Valid as source:** Not stated +- **Valid as destination:** Not stated +- **Forwardable:** Not stated +- **Globally reachable:** Not stated +- **Reserved by protocol:** Not stated +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-088-099-002--32--iana-special.md b/registry-ips/192-088-099-002--32--iana-special.md new file mode 100644 index 0000000..4dd1afc --- /dev/null +++ b/registry-ips/192-088-099-002--32--iana-special.md @@ -0,0 +1,28 @@ + +# 192.88.99.2/32 — 6a44-relay anycast address + +## Who is this IP range? + +IANA identifies **192.88.99.2/32** as **6a44-relay anycast address** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.88.99.2/32` +- **Name:** 6a44-relay anycast address +- **RFC/reference:** [RFC6751] +- **Allocation date:** 2012-10 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-168-000-000--16--iana-special.md b/registry-ips/192-168-000-000--16--iana-special.md new file mode 100644 index 0000000..f7528eb --- /dev/null +++ b/registry-ips/192-168-000-000--16--iana-special.md @@ -0,0 +1,28 @@ + +# 192.168.0.0/16 — Private-Use + +## Who is this IP range? + +IANA identifies **192.168.0.0/16** as **Private-Use** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.168.0.0/16` +- **Name:** Private-Use +- **RFC/reference:** [RFC1918] +- **Allocation date:** 1996-02 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/192-175-048-000--24--iana-special.md b/registry-ips/192-175-048-000--24--iana-special.md new file mode 100644 index 0000000..07dfe28 --- /dev/null +++ b/registry-ips/192-175-048-000--24--iana-special.md @@ -0,0 +1,28 @@ + +# 192.175.48.0/24 — Direct Delegation AS112 Service + +## Who is this IP range? + +IANA identifies **192.175.48.0/24** as **Direct Delegation AS112 Service** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `192.175.48.0/24` +- **Name:** Direct Delegation AS112 Service +- **RFC/reference:** [RFC7534] +- **Allocation date:** 1996-01 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** True +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/193-000-000-000--08--ripe-ncc.md b/registry-ips/193-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..db32579 --- /dev/null +++ b/registry-ips/193-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 193.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **193.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `193.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/194-000-000-000--08--ripe-ncc.md b/registry-ips/194-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..c6f9604 --- /dev/null +++ b/registry-ips/194-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 194.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **194.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `194.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/195-000-000-000--08--ripe-ncc.md b/registry-ips/195-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..5b36ceb --- /dev/null +++ b/registry-ips/195-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 195.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **195.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `195.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/196-000-000-000--08--afrinic.md b/registry-ips/196-000-000-000--08--afrinic.md new file mode 100644 index 0000000..b90c0c0 --- /dev/null +++ b/registry-ips/196-000-000-000--08--afrinic.md @@ -0,0 +1,28 @@ + +# 196.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **196.0.0.0/8** to **Administered by AFRINIC** and the RDAP authority maps to **afrinic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `196.0.0.0/8` +- **IANA designation:** Administered by AFRINIC +- **Registry suffix:** `afrinic` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.afrinic.net +- **RDAP authority:** https://rdap.afrinic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/197-000-000-000--08--afrinic.md b/registry-ips/197-000-000-000--08--afrinic.md new file mode 100644 index 0000000..5be4681 --- /dev/null +++ b/registry-ips/197-000-000-000--08--afrinic.md @@ -0,0 +1,28 @@ + +# 197.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **197.0.0.0/8** to **AFRINIC** and the RDAP authority maps to **afrinic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `197.0.0.0/8` +- **IANA designation:** AFRINIC +- **Registry suffix:** `afrinic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2008-10 +- **WHOIS authority:** whois.afrinic.net +- **RDAP authority:** https://rdap.afrinic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/198-000-000-000--08--arin.md b/registry-ips/198-000-000-000--08--arin.md new file mode 100644 index 0000000..de1f979 --- /dev/null +++ b/registry-ips/198-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 198.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **198.0.0.0/8** to **Administered by ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `198.0.0.0/8` +- **IANA designation:** Administered by ARIN +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** [12] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/198-018-000-000--15--iana-special.md b/registry-ips/198-018-000-000--15--iana-special.md new file mode 100644 index 0000000..7ba1e88 --- /dev/null +++ b/registry-ips/198-018-000-000--15--iana-special.md @@ -0,0 +1,28 @@ + +# 198.18.0.0/15 — Benchmarking + +## Who is this IP range? + +IANA identifies **198.18.0.0/15** as **Benchmarking** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `198.18.0.0/15` +- **Name:** Benchmarking +- **RFC/reference:** [RFC2544] +- **Allocation date:** 1999-03 +- **Termination date:** N/A +- **Valid as source:** True +- **Valid as destination:** True +- **Forwardable:** True +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/198-051-100-000--24--iana-special.md b/registry-ips/198-051-100-000--24--iana-special.md new file mode 100644 index 0000000..999114b --- /dev/null +++ b/registry-ips/198-051-100-000--24--iana-special.md @@ -0,0 +1,28 @@ + +# 198.51.100.0/24 — Documentation (TEST-NET-2) + +## Who is this IP range? + +IANA identifies **198.51.100.0/24** as **Documentation (TEST-NET-2)** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `198.51.100.0/24` +- **Name:** Documentation (TEST-NET-2) +- **RFC/reference:** [RFC5737] +- **Allocation date:** 2010-01 +- **Termination date:** N/A +- **Valid as source:** False +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/199-000-000-000--08--arin.md b/registry-ips/199-000-000-000--08--arin.md new file mode 100644 index 0000000..c7e3d20 --- /dev/null +++ b/registry-ips/199-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 199.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **199.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `199.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/200-000-000-000--08--lacnic.md b/registry-ips/200-000-000-000--08--lacnic.md new file mode 100644 index 0000000..948e5f6 --- /dev/null +++ b/registry-ips/200-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 200.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **200.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `200.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2002-11 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/201-000-000-000--08--lacnic.md b/registry-ips/201-000-000-000--08--lacnic.md new file mode 100644 index 0000000..f7f94e9 --- /dev/null +++ b/registry-ips/201-000-000-000--08--lacnic.md @@ -0,0 +1,28 @@ + +# 201.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **201.0.0.0/8** to **LACNIC** and the RDAP authority maps to **lacnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `201.0.0.0/8` +- **IANA designation:** LACNIC +- **Registry suffix:** `lacnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2003-04 +- **WHOIS authority:** whois.lacnic.net +- **RDAP authority:** https://rdap.lacnic.net/rdap/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/202-000-000-000--08--apnic.md b/registry-ips/202-000-000-000--08--apnic.md new file mode 100644 index 0000000..9a705a5 --- /dev/null +++ b/registry-ips/202-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 202.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **202.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `202.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/203-000-000-000--08--apnic.md b/registry-ips/203-000-000-000--08--apnic.md new file mode 100644 index 0000000..ddf4cb4 --- /dev/null +++ b/registry-ips/203-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 203.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **203.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `203.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1993-05 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** [13] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/203-000-113-000--24--iana-special.md b/registry-ips/203-000-113-000--24--iana-special.md new file mode 100644 index 0000000..45bd5bd --- /dev/null +++ b/registry-ips/203-000-113-000--24--iana-special.md @@ -0,0 +1,28 @@ + +# 203.0.113.0/24 — Documentation (TEST-NET-3) + +## Who is this IP range? + +IANA identifies **203.0.113.0/24** as **Documentation (TEST-NET-3)** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `203.0.113.0/24` +- **Name:** Documentation (TEST-NET-3) +- **RFC/reference:** [RFC5737] +- **Allocation date:** 2010-01 +- **Termination date:** N/A +- **Valid as source:** False +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** False +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/204-000-000-000--08--arin.md b/registry-ips/204-000-000-000--08--arin.md new file mode 100644 index 0000000..7e466d3 --- /dev/null +++ b/registry-ips/204-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 204.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **204.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `204.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1994-03 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/205-000-000-000--08--arin.md b/registry-ips/205-000-000-000--08--arin.md new file mode 100644 index 0000000..c0dcb9c --- /dev/null +++ b/registry-ips/205-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 205.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **205.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `205.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1994-03 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/206-000-000-000--08--arin.md b/registry-ips/206-000-000-000--08--arin.md new file mode 100644 index 0000000..3a26f9a --- /dev/null +++ b/registry-ips/206-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 206.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **206.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `206.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1995-04 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/207-000-000-000--08--arin.md b/registry-ips/207-000-000-000--08--arin.md new file mode 100644 index 0000000..bbffc7d --- /dev/null +++ b/registry-ips/207-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 207.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **207.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `207.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1995-11 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/208-000-000-000--08--arin.md b/registry-ips/208-000-000-000--08--arin.md new file mode 100644 index 0000000..1ac7984 --- /dev/null +++ b/registry-ips/208-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 208.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **208.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `208.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1996-04 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/209-000-000-000--08--arin.md b/registry-ips/209-000-000-000--08--arin.md new file mode 100644 index 0000000..a98a5aa --- /dev/null +++ b/registry-ips/209-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 209.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **209.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `209.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1996-06 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/210-000-000-000--08--apnic.md b/registry-ips/210-000-000-000--08--apnic.md new file mode 100644 index 0000000..4c67771 --- /dev/null +++ b/registry-ips/210-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 210.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **210.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `210.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1996-06 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/211-000-000-000--08--apnic.md b/registry-ips/211-000-000-000--08--apnic.md new file mode 100644 index 0000000..b45246f --- /dev/null +++ b/registry-ips/211-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 211.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **211.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `211.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1996-06 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/212-000-000-000--08--ripe-ncc.md b/registry-ips/212-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..d64cad8 --- /dev/null +++ b/registry-ips/212-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 212.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **212.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `212.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1997-10 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/213-000-000-000--08--ripe-ncc.md b/registry-ips/213-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..3905ec0 --- /dev/null +++ b/registry-ips/213-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 213.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **213.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `213.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1993-10 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/214-000-000-000--08--arin.md b/registry-ips/214-000-000-000--08--arin.md new file mode 100644 index 0000000..983e5ac --- /dev/null +++ b/registry-ips/214-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 214.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **214.0.0.0/8** to **US-DOD** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `214.0.0.0/8` +- **IANA designation:** US-DOD +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1998-03 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/215-000-000-000--08--arin.md b/registry-ips/215-000-000-000--08--arin.md new file mode 100644 index 0000000..596999d --- /dev/null +++ b/registry-ips/215-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 215.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **215.0.0.0/8** to **US-DOD** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `215.0.0.0/8` +- **IANA designation:** US-DOD +- **Registry suffix:** `arin` +- **IANA status:** LEGACY +- **Allocation/record date:** 1998-03 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/216-000-000-000--08--arin.md b/registry-ips/216-000-000-000--08--arin.md new file mode 100644 index 0000000..f6b349c --- /dev/null +++ b/registry-ips/216-000-000-000--08--arin.md @@ -0,0 +1,28 @@ + +# 216.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **216.0.0.0/8** to **ARIN** and the RDAP authority maps to **arin**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `216.0.0.0/8` +- **IANA designation:** ARIN +- **Registry suffix:** `arin` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 1998-04 +- **WHOIS authority:** whois.arin.net +- **RDAP authority:** https://rdap.arin.net/registry +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/217-000-000-000--08--ripe-ncc.md b/registry-ips/217-000-000-000--08--ripe-ncc.md new file mode 100644 index 0000000..f3ec97a --- /dev/null +++ b/registry-ips/217-000-000-000--08--ripe-ncc.md @@ -0,0 +1,28 @@ + +# 217.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **217.0.0.0/8** to **RIPE NCC** and the RDAP authority maps to **ripe-ncc**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `217.0.0.0/8` +- **IANA designation:** RIPE NCC +- **Registry suffix:** `ripe-ncc` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2000-06 +- **WHOIS authority:** whois.ripe.net +- **RDAP authority:** https://rdap.db.ripe.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/218-000-000-000--08--apnic.md b/registry-ips/218-000-000-000--08--apnic.md new file mode 100644 index 0000000..1aae4ae --- /dev/null +++ b/registry-ips/218-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 218.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **218.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `218.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2000-12 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/219-000-000-000--08--apnic.md b/registry-ips/219-000-000-000--08--apnic.md new file mode 100644 index 0000000..ce9597e --- /dev/null +++ b/registry-ips/219-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 219.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **219.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `219.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2001-09 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/220-000-000-000--08--apnic.md b/registry-ips/220-000-000-000--08--apnic.md new file mode 100644 index 0000000..bdba84a --- /dev/null +++ b/registry-ips/220-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 220.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **220.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `220.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2001-12 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/221-000-000-000--08--apnic.md b/registry-ips/221-000-000-000--08--apnic.md new file mode 100644 index 0000000..867719d --- /dev/null +++ b/registry-ips/221-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 221.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **221.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `221.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2002-07 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/222-000-000-000--08--apnic.md b/registry-ips/222-000-000-000--08--apnic.md new file mode 100644 index 0000000..2839d21 --- /dev/null +++ b/registry-ips/222-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 222.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **222.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `222.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2003-02 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/223-000-000-000--08--apnic.md b/registry-ips/223-000-000-000--08--apnic.md new file mode 100644 index 0000000..e32707c --- /dev/null +++ b/registry-ips/223-000-000-000--08--apnic.md @@ -0,0 +1,28 @@ + +# 223.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +At the top-level `/8` registry layer, IANA designates **223.0.0.0/8** to **APNIC** and the RDAP authority maps to **apnic**. This does not identify one holder or operator for every address inside the block; detailed attribution requires more-specific RDAP and BGP research. + +## Registry record + +- **Range:** `223.0.0.0/8` +- **IANA designation:** APNIC +- **Registry suffix:** `apnic` +- **IANA status:** ALLOCATED +- **Allocation/record date:** 2010-04 +- **WHOIS authority:** whois.apnic.net +- **RDAP authority:** https://rdap.apnic.net/ +- **IANA note:** None +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/224-000-000-000--08--iana.md b/registry-ips/224-000-000-000--08--iana.md new file mode 100644 index 0000000..3d04399 --- /dev/null +++ b/registry-ips/224-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 224.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **224.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `224.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/225-000-000-000--08--iana.md b/registry-ips/225-000-000-000--08--iana.md new file mode 100644 index 0000000..6c36aef --- /dev/null +++ b/registry-ips/225-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 225.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **225.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `225.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/226-000-000-000--08--iana.md b/registry-ips/226-000-000-000--08--iana.md new file mode 100644 index 0000000..00c2455 --- /dev/null +++ b/registry-ips/226-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 226.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **226.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `226.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/227-000-000-000--08--iana.md b/registry-ips/227-000-000-000--08--iana.md new file mode 100644 index 0000000..4a4ced3 --- /dev/null +++ b/registry-ips/227-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 227.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **227.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `227.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/228-000-000-000--08--iana.md b/registry-ips/228-000-000-000--08--iana.md new file mode 100644 index 0000000..24bdf3e --- /dev/null +++ b/registry-ips/228-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 228.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **228.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `228.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/229-000-000-000--08--iana.md b/registry-ips/229-000-000-000--08--iana.md new file mode 100644 index 0000000..0dd628d --- /dev/null +++ b/registry-ips/229-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 229.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **229.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `229.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/230-000-000-000--08--iana.md b/registry-ips/230-000-000-000--08--iana.md new file mode 100644 index 0000000..754b4d2 --- /dev/null +++ b/registry-ips/230-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 230.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **230.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `230.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/231-000-000-000--08--iana.md b/registry-ips/231-000-000-000--08--iana.md new file mode 100644 index 0000000..ef347ef --- /dev/null +++ b/registry-ips/231-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 231.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **231.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `231.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/232-000-000-000--08--iana.md b/registry-ips/232-000-000-000--08--iana.md new file mode 100644 index 0000000..dbe3d1e --- /dev/null +++ b/registry-ips/232-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 232.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **232.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `232.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/233-000-000-000--08--iana.md b/registry-ips/233-000-000-000--08--iana.md new file mode 100644 index 0000000..54cf4d4 --- /dev/null +++ b/registry-ips/233-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 233.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **233.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `233.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/234-000-000-000--08--iana.md b/registry-ips/234-000-000-000--08--iana.md new file mode 100644 index 0000000..d466e4f --- /dev/null +++ b/registry-ips/234-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 234.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **234.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `234.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14][15] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/235-000-000-000--08--iana.md b/registry-ips/235-000-000-000--08--iana.md new file mode 100644 index 0000000..75fe502 --- /dev/null +++ b/registry-ips/235-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 235.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **235.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `235.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/236-000-000-000--08--iana.md b/registry-ips/236-000-000-000--08--iana.md new file mode 100644 index 0000000..03082fa --- /dev/null +++ b/registry-ips/236-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 236.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **236.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `236.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/237-000-000-000--08--iana.md b/registry-ips/237-000-000-000--08--iana.md new file mode 100644 index 0000000..7793f19 --- /dev/null +++ b/registry-ips/237-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 237.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **237.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `237.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/238-000-000-000--08--iana.md b/registry-ips/238-000-000-000--08--iana.md new file mode 100644 index 0000000..72f4103 --- /dev/null +++ b/registry-ips/238-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 238.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **238.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `238.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/239-000-000-000--08--iana.md b/registry-ips/239-000-000-000--08--iana.md new file mode 100644 index 0000000..c0cfcf4 --- /dev/null +++ b/registry-ips/239-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 239.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **239.0.0.0/8** as **Multicast** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `239.0.0.0/8` +- **IANA designation:** Multicast +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [14][16] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/240-000-000-000--04--iana-special.md b/registry-ips/240-000-000-000--04--iana-special.md new file mode 100644 index 0000000..d7fdb43 --- /dev/null +++ b/registry-ips/240-000-000-000--04--iana-special.md @@ -0,0 +1,28 @@ + +# 240.0.0.0/4 — Reserved + +## Who is this IP range? + +IANA identifies **240.0.0.0/4** as **Reserved** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `240.0.0.0/4` +- **Name:** Reserved +- **RFC/reference:** [RFC1112], Section 4 +- **Allocation date:** 1989-08 +- **Termination date:** N/A +- **Valid as source:** False +- **Valid as destination:** False +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** True +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/240-000-000-000--08--iana.md b/registry-ips/240-000-000-000--08--iana.md new file mode 100644 index 0000000..3d5ede1 --- /dev/null +++ b/registry-ips/240-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 240.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **240.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `240.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/241-000-000-000--08--iana.md b/registry-ips/241-000-000-000--08--iana.md new file mode 100644 index 0000000..2dc3779 --- /dev/null +++ b/registry-ips/241-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 241.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **241.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `241.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/242-000-000-000--08--iana.md b/registry-ips/242-000-000-000--08--iana.md new file mode 100644 index 0000000..f86c9b4 --- /dev/null +++ b/registry-ips/242-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 242.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **242.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `242.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/243-000-000-000--08--iana.md b/registry-ips/243-000-000-000--08--iana.md new file mode 100644 index 0000000..0ff8dc2 --- /dev/null +++ b/registry-ips/243-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 243.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **243.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `243.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/244-000-000-000--08--iana.md b/registry-ips/244-000-000-000--08--iana.md new file mode 100644 index 0000000..f51edaa --- /dev/null +++ b/registry-ips/244-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 244.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **244.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `244.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/245-000-000-000--08--iana.md b/registry-ips/245-000-000-000--08--iana.md new file mode 100644 index 0000000..e913d5c --- /dev/null +++ b/registry-ips/245-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 245.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **245.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `245.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/246-000-000-000--08--iana.md b/registry-ips/246-000-000-000--08--iana.md new file mode 100644 index 0000000..7149ea6 --- /dev/null +++ b/registry-ips/246-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 246.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **246.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `246.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/247-000-000-000--08--iana.md b/registry-ips/247-000-000-000--08--iana.md new file mode 100644 index 0000000..fd82b86 --- /dev/null +++ b/registry-ips/247-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 247.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **247.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `247.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/248-000-000-000--08--iana.md b/registry-ips/248-000-000-000--08--iana.md new file mode 100644 index 0000000..f4c0097 --- /dev/null +++ b/registry-ips/248-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 248.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **248.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `248.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/249-000-000-000--08--iana.md b/registry-ips/249-000-000-000--08--iana.md new file mode 100644 index 0000000..382d670 --- /dev/null +++ b/registry-ips/249-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 249.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **249.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `249.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/250-000-000-000--08--iana.md b/registry-ips/250-000-000-000--08--iana.md new file mode 100644 index 0000000..4a69e4e --- /dev/null +++ b/registry-ips/250-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 250.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **250.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `250.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/251-000-000-000--08--iana.md b/registry-ips/251-000-000-000--08--iana.md new file mode 100644 index 0000000..643be13 --- /dev/null +++ b/registry-ips/251-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 251.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **251.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `251.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/252-000-000-000--08--iana.md b/registry-ips/252-000-000-000--08--iana.md new file mode 100644 index 0000000..49c99da --- /dev/null +++ b/registry-ips/252-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 252.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **252.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `252.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/253-000-000-000--08--iana.md b/registry-ips/253-000-000-000--08--iana.md new file mode 100644 index 0000000..b922333 --- /dev/null +++ b/registry-ips/253-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 253.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **253.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `253.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/254-000-000-000--08--iana.md b/registry-ips/254-000-000-000--08--iana.md new file mode 100644 index 0000000..8e849ac --- /dev/null +++ b/registry-ips/254-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 254.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **254.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `254.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/255-000-000-000--08--iana.md b/registry-ips/255-000-000-000--08--iana.md new file mode 100644 index 0000000..a05bdcc --- /dev/null +++ b/registry-ips/255-000-000-000--08--iana.md @@ -0,0 +1,28 @@ + +# 255.0.0.0/8 — IANA top-level IPv4 registry + +## Who is this IP range? + +IANA records **255.0.0.0/8** as **Future use** with status **reserved**. It is not presented here as an ordinary allocation with one network operator. + +## Registry record + +- **Range:** `255.0.0.0/8` +- **IANA designation:** Future use +- **Registry suffix:** `iana` +- **IANA status:** RESERVED +- **Allocation/record date:** 1981-09 +- **WHOIS authority:** Not stated +- **RDAP authority:** Not stated +- **IANA note:** [17][18] +- **Checked:** 2026-07-22 + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry](https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml), checked 2026-07-22 diff --git a/registry-ips/255-255-255-255--32--iana-special.md b/registry-ips/255-255-255-255--32--iana-special.md new file mode 100644 index 0000000..8c2e476 --- /dev/null +++ b/registry-ips/255-255-255-255--32--iana-special.md @@ -0,0 +1,28 @@ + +# 255.255.255.255/32 — Limited Broadcast + +## Who is this IP range? + +IANA identifies **255.255.255.255/32** as **Limited Broadcast** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `255.255.255.255/32` +- **Name:** Limited Broadcast +- **RFC/reference:** [RFC8190] [RFC919], Section 7 +- **Allocation date:** 1984-10 +- **Termination date:** N/A +- **Valid as source:** False +- **Valid as destination:** True +- **Forwardable:** False +- **Globally reachable:** False +- **Reserved by protocol:** True +- **Checked:** 2026-07-22 + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml), checked 2026-07-22 diff --git a/registry-ips/IPV4-INDEX.md b/registry-ips/IPV4-INDEX.md new file mode 100644 index 0000000..d54bfbd --- /dev/null +++ b/registry-ips/IPV4-INDEX.md @@ -0,0 +1,321 @@ + +# Complete IANA IPv4 range index + +Generated from authoritative IANA registries and checked **2026-07-22**. + +## Coverage + +- **256 top-level `/8` records**, covering all IPv4 addresses from `0.0.0.0` through `255.255.255.255` without gaps. +- **26 expanded special-purpose prefixes** from the IANA IPv4 Special-Purpose Address Registry. +- More-specific manual research records and placeholders remain alongside these authoritative baselines. + +## Top-level counts + +### By RDAP registry authority + +- `afrinic`: 6 +- `apnic`: 51 +- `arin`: 111 +- `iana`: 35 +- `lacnic`: 10 +- `ripe-ncc`: 43 + +### By IANA status + +- `allocated`: 129 +- `legacy`: 92 +- `reserved`: 35 + +## All top-level IPv4 /8 ranges + +| Range | IANA designation | Status | Registry/RDAP | Record | +|---|---|---|---|---| +| `0.0.0.0/8` | IANA - Local Identification | RESERVED | `iana` | [record](000-000-000-000--08--iana.md) | +| `1.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](001-000-000-000--08--apnic.md) | +| `2.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](002-000-000-000--08--ripe-ncc.md) | +| `3.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](003-000-000-000--08--arin.md) | +| `4.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](004-000-000-000--08--arin.md) | +| `5.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](005-000-000-000--08--ripe-ncc.md) | +| `6.0.0.0/8` | Army Information Systems Center | LEGACY | `arin` | [record](006-000-000-000--08--arin.md) | +| `7.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](007-000-000-000--08--arin.md) | +| `8.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](008-000-000-000--08--arin.md) | +| `9.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](009-000-000-000--08--arin.md) | +| `10.0.0.0/8` | IANA - Private Use | RESERVED | `iana` | [record](010-000-000-000--08--iana.md) | +| `11.0.0.0/8` | DoD Intel Information Systems | LEGACY | `arin` | [record](011-000-000-000--08--arin.md) | +| `12.0.0.0/8` | AT&T Bell Laboratories | LEGACY | `arin` | [record](012-000-000-000--08--arin.md) | +| `13.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](013-000-000-000--08--arin.md) | +| `14.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](014-000-000-000--08--apnic.md) | +| `15.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](015-000-000-000--08--arin.md) | +| `16.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](016-000-000-000--08--arin.md) | +| `17.0.0.0/8` | Apple Computer Inc. | LEGACY | `arin` | [record](017-000-000-000--08--arin.md) | +| `18.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](018-000-000-000--08--arin.md) | +| `19.0.0.0/8` | Ford Motor Company | LEGACY | `arin` | [record](019-000-000-000--08--arin.md) | +| `20.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](020-000-000-000--08--arin.md) | +| `21.0.0.0/8` | DDN-RVN | LEGACY | `arin` | [record](021-000-000-000--08--arin.md) | +| `22.0.0.0/8` | Defense Information Systems Agency | LEGACY | `arin` | [record](022-000-000-000--08--arin.md) | +| `23.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](023-000-000-000--08--arin.md) | +| `24.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](024-000-000-000--08--arin.md) | +| `25.0.0.0/8` | Administered by RIPE NCC | LEGACY | `ripe-ncc` | [record](025-000-000-000--08--ripe-ncc.md) | +| `26.0.0.0/8` | Defense Information Systems Agency | LEGACY | `arin` | [record](026-000-000-000--08--arin.md) | +| `27.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](027-000-000-000--08--apnic.md) | +| `28.0.0.0/8` | DSI-North | LEGACY | `arin` | [record](028-000-000-000--08--arin.md) | +| `29.0.0.0/8` | Defense Information Systems Agency | LEGACY | `arin` | [record](029-000-000-000--08--arin.md) | +| `30.0.0.0/8` | Defense Information Systems Agency | LEGACY | `arin` | [record](030-000-000-000--08--arin.md) | +| `31.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](031-000-000-000--08--ripe-ncc.md) | +| `32.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](032-000-000-000--08--arin.md) | +| `33.0.0.0/8` | DLA Systems Automation Center | LEGACY | `arin` | [record](033-000-000-000--08--arin.md) | +| `34.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](034-000-000-000--08--arin.md) | +| `35.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](035-000-000-000--08--arin.md) | +| `36.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](036-000-000-000--08--apnic.md) | +| `37.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](037-000-000-000--08--ripe-ncc.md) | +| `38.0.0.0/8` | PSINet, Inc. | LEGACY | `arin` | [record](038-000-000-000--08--arin.md) | +| `39.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](039-000-000-000--08--apnic.md) | +| `40.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](040-000-000-000--08--arin.md) | +| `41.0.0.0/8` | AFRINIC | ALLOCATED | `afrinic` | [record](041-000-000-000--08--afrinic.md) | +| `42.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](042-000-000-000--08--apnic.md) | +| `43.0.0.0/8` | Administered by APNIC | LEGACY | `apnic` | [record](043-000-000-000--08--apnic.md) | +| `44.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](044-000-000-000--08--arin.md) | +| `45.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](045-000-000-000--08--arin.md) | +| `46.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](046-000-000-000--08--ripe-ncc.md) | +| `47.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](047-000-000-000--08--arin.md) | +| `48.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](048-000-000-000--08--arin.md) | +| `49.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](049-000-000-000--08--apnic.md) | +| `50.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](050-000-000-000--08--arin.md) | +| `51.0.0.0/8` | Administered by RIPE NCC | LEGACY | `ripe-ncc` | [record](051-000-000-000--08--ripe-ncc.md) | +| `52.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](052-000-000-000--08--arin.md) | +| `53.0.0.0/8` | Daimler AG | LEGACY | `ripe-ncc` | [record](053-000-000-000--08--ripe-ncc.md) | +| `54.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](054-000-000-000--08--arin.md) | +| `55.0.0.0/8` | DoD Network Information Center | LEGACY | `arin` | [record](055-000-000-000--08--arin.md) | +| `56.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](056-000-000-000--08--arin.md) | +| `57.0.0.0/8` | Administered by RIPE NCC | LEGACY | `ripe-ncc` | [record](057-000-000-000--08--ripe-ncc.md) | +| `58.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](058-000-000-000--08--apnic.md) | +| `59.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](059-000-000-000--08--apnic.md) | +| `60.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](060-000-000-000--08--apnic.md) | +| `61.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](061-000-000-000--08--apnic.md) | +| `62.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](062-000-000-000--08--ripe-ncc.md) | +| `63.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](063-000-000-000--08--arin.md) | +| `64.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](064-000-000-000--08--arin.md) | +| `65.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](065-000-000-000--08--arin.md) | +| `66.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](066-000-000-000--08--arin.md) | +| `67.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](067-000-000-000--08--arin.md) | +| `68.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](068-000-000-000--08--arin.md) | +| `69.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](069-000-000-000--08--arin.md) | +| `70.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](070-000-000-000--08--arin.md) | +| `71.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](071-000-000-000--08--arin.md) | +| `72.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](072-000-000-000--08--arin.md) | +| `73.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](073-000-000-000--08--arin.md) | +| `74.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](074-000-000-000--08--arin.md) | +| `75.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](075-000-000-000--08--arin.md) | +| `76.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](076-000-000-000--08--arin.md) | +| `77.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](077-000-000-000--08--ripe-ncc.md) | +| `78.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](078-000-000-000--08--ripe-ncc.md) | +| `79.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](079-000-000-000--08--ripe-ncc.md) | +| `80.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](080-000-000-000--08--ripe-ncc.md) | +| `81.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](081-000-000-000--08--ripe-ncc.md) | +| `82.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](082-000-000-000--08--ripe-ncc.md) | +| `83.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](083-000-000-000--08--ripe-ncc.md) | +| `84.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](084-000-000-000--08--ripe-ncc.md) | +| `85.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](085-000-000-000--08--ripe-ncc.md) | +| `86.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](086-000-000-000--08--ripe-ncc.md) | +| `87.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](087-000-000-000--08--ripe-ncc.md) | +| `88.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](088-000-000-000--08--ripe-ncc.md) | +| `89.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](089-000-000-000--08--ripe-ncc.md) | +| `90.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](090-000-000-000--08--ripe-ncc.md) | +| `91.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](091-000-000-000--08--ripe-ncc.md) | +| `92.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](092-000-000-000--08--ripe-ncc.md) | +| `93.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](093-000-000-000--08--ripe-ncc.md) | +| `94.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](094-000-000-000--08--ripe-ncc.md) | +| `95.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](095-000-000-000--08--ripe-ncc.md) | +| `96.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](096-000-000-000--08--arin.md) | +| `97.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](097-000-000-000--08--arin.md) | +| `98.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](098-000-000-000--08--arin.md) | +| `99.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](099-000-000-000--08--arin.md) | +| `100.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](100-000-000-000--08--arin.md) | +| `101.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](101-000-000-000--08--apnic.md) | +| `102.0.0.0/8` | AFRINIC | ALLOCATED | `afrinic` | [record](102-000-000-000--08--afrinic.md) | +| `103.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](103-000-000-000--08--apnic.md) | +| `104.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](104-000-000-000--08--arin.md) | +| `105.0.0.0/8` | AFRINIC | ALLOCATED | `afrinic` | [record](105-000-000-000--08--afrinic.md) | +| `106.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](106-000-000-000--08--apnic.md) | +| `107.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](107-000-000-000--08--arin.md) | +| `108.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](108-000-000-000--08--arin.md) | +| `109.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](109-000-000-000--08--ripe-ncc.md) | +| `110.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](110-000-000-000--08--apnic.md) | +| `111.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](111-000-000-000--08--apnic.md) | +| `112.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](112-000-000-000--08--apnic.md) | +| `113.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](113-000-000-000--08--apnic.md) | +| `114.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](114-000-000-000--08--apnic.md) | +| `115.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](115-000-000-000--08--apnic.md) | +| `116.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](116-000-000-000--08--apnic.md) | +| `117.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](117-000-000-000--08--apnic.md) | +| `118.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](118-000-000-000--08--apnic.md) | +| `119.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](119-000-000-000--08--apnic.md) | +| `120.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](120-000-000-000--08--apnic.md) | +| `121.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](121-000-000-000--08--apnic.md) | +| `122.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](122-000-000-000--08--apnic.md) | +| `123.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](123-000-000-000--08--apnic.md) | +| `124.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](124-000-000-000--08--apnic.md) | +| `125.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](125-000-000-000--08--apnic.md) | +| `126.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](126-000-000-000--08--apnic.md) | +| `127.0.0.0/8` | IANA - Loopback | RESERVED | `iana` | [record](127-000-000-000--08--iana.md) | +| `128.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](128-000-000-000--08--arin.md) | +| `129.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](129-000-000-000--08--arin.md) | +| `130.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](130-000-000-000--08--arin.md) | +| `131.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](131-000-000-000--08--arin.md) | +| `132.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](132-000-000-000--08--arin.md) | +| `133.0.0.0/8` | Administered by APNIC | LEGACY | `apnic` | [record](133-000-000-000--08--apnic.md) | +| `134.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](134-000-000-000--08--arin.md) | +| `135.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](135-000-000-000--08--arin.md) | +| `136.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](136-000-000-000--08--arin.md) | +| `137.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](137-000-000-000--08--arin.md) | +| `138.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](138-000-000-000--08--arin.md) | +| `139.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](139-000-000-000--08--arin.md) | +| `140.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](140-000-000-000--08--arin.md) | +| `141.0.0.0/8` | Administered by RIPE NCC | LEGACY | `ripe-ncc` | [record](141-000-000-000--08--ripe-ncc.md) | +| `142.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](142-000-000-000--08--arin.md) | +| `143.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](143-000-000-000--08--arin.md) | +| `144.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](144-000-000-000--08--arin.md) | +| `145.0.0.0/8` | Administered by RIPE NCC | LEGACY | `ripe-ncc` | [record](145-000-000-000--08--ripe-ncc.md) | +| `146.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](146-000-000-000--08--arin.md) | +| `147.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](147-000-000-000--08--arin.md) | +| `148.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](148-000-000-000--08--arin.md) | +| `149.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](149-000-000-000--08--arin.md) | +| `150.0.0.0/8` | Administered by APNIC | LEGACY | `apnic` | [record](150-000-000-000--08--apnic.md) | +| `151.0.0.0/8` | Administered by RIPE NCC | LEGACY | `ripe-ncc` | [record](151-000-000-000--08--ripe-ncc.md) | +| `152.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](152-000-000-000--08--arin.md) | +| `153.0.0.0/8` | Administered by APNIC | LEGACY | `apnic` | [record](153-000-000-000--08--apnic.md) | +| `154.0.0.0/8` | Administered by AFRINIC | LEGACY | `afrinic` | [record](154-000-000-000--08--afrinic.md) | +| `155.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](155-000-000-000--08--arin.md) | +| `156.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](156-000-000-000--08--arin.md) | +| `157.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](157-000-000-000--08--arin.md) | +| `158.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](158-000-000-000--08--arin.md) | +| `159.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](159-000-000-000--08--arin.md) | +| `160.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](160-000-000-000--08--arin.md) | +| `161.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](161-000-000-000--08--arin.md) | +| `162.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](162-000-000-000--08--arin.md) | +| `163.0.0.0/8` | Administered by APNIC | LEGACY | `apnic` | [record](163-000-000-000--08--apnic.md) | +| `164.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](164-000-000-000--08--arin.md) | +| `165.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](165-000-000-000--08--arin.md) | +| `166.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](166-000-000-000--08--arin.md) | +| `167.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](167-000-000-000--08--arin.md) | +| `168.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](168-000-000-000--08--arin.md) | +| `169.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](169-000-000-000--08--arin.md) | +| `170.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](170-000-000-000--08--arin.md) | +| `171.0.0.0/8` | Administered by APNIC | LEGACY | `apnic` | [record](171-000-000-000--08--apnic.md) | +| `172.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](172-000-000-000--08--arin.md) | +| `173.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](173-000-000-000--08--arin.md) | +| `174.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](174-000-000-000--08--arin.md) | +| `175.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](175-000-000-000--08--apnic.md) | +| `176.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](176-000-000-000--08--ripe-ncc.md) | +| `177.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](177-000-000-000--08--lacnic.md) | +| `178.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](178-000-000-000--08--ripe-ncc.md) | +| `179.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](179-000-000-000--08--lacnic.md) | +| `180.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](180-000-000-000--08--apnic.md) | +| `181.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](181-000-000-000--08--lacnic.md) | +| `182.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](182-000-000-000--08--apnic.md) | +| `183.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](183-000-000-000--08--apnic.md) | +| `184.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](184-000-000-000--08--arin.md) | +| `185.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](185-000-000-000--08--ripe-ncc.md) | +| `186.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](186-000-000-000--08--lacnic.md) | +| `187.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](187-000-000-000--08--lacnic.md) | +| `188.0.0.0/8` | Administered by RIPE NCC | LEGACY | `ripe-ncc` | [record](188-000-000-000--08--ripe-ncc.md) | +| `189.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](189-000-000-000--08--lacnic.md) | +| `190.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](190-000-000-000--08--lacnic.md) | +| `191.0.0.0/8` | Administered by LACNIC | LEGACY | `lacnic` | [record](191-000-000-000--08--lacnic.md) | +| `192.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](192-000-000-000--08--arin.md) | +| `193.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](193-000-000-000--08--ripe-ncc.md) | +| `194.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](194-000-000-000--08--ripe-ncc.md) | +| `195.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](195-000-000-000--08--ripe-ncc.md) | +| `196.0.0.0/8` | Administered by AFRINIC | LEGACY | `afrinic` | [record](196-000-000-000--08--afrinic.md) | +| `197.0.0.0/8` | AFRINIC | ALLOCATED | `afrinic` | [record](197-000-000-000--08--afrinic.md) | +| `198.0.0.0/8` | Administered by ARIN | LEGACY | `arin` | [record](198-000-000-000--08--arin.md) | +| `199.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](199-000-000-000--08--arin.md) | +| `200.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](200-000-000-000--08--lacnic.md) | +| `201.0.0.0/8` | LACNIC | ALLOCATED | `lacnic` | [record](201-000-000-000--08--lacnic.md) | +| `202.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](202-000-000-000--08--apnic.md) | +| `203.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](203-000-000-000--08--apnic.md) | +| `204.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](204-000-000-000--08--arin.md) | +| `205.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](205-000-000-000--08--arin.md) | +| `206.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](206-000-000-000--08--arin.md) | +| `207.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](207-000-000-000--08--arin.md) | +| `208.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](208-000-000-000--08--arin.md) | +| `209.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](209-000-000-000--08--arin.md) | +| `210.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](210-000-000-000--08--apnic.md) | +| `211.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](211-000-000-000--08--apnic.md) | +| `212.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](212-000-000-000--08--ripe-ncc.md) | +| `213.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](213-000-000-000--08--ripe-ncc.md) | +| `214.0.0.0/8` | US-DOD | LEGACY | `arin` | [record](214-000-000-000--08--arin.md) | +| `215.0.0.0/8` | US-DOD | LEGACY | `arin` | [record](215-000-000-000--08--arin.md) | +| `216.0.0.0/8` | ARIN | ALLOCATED | `arin` | [record](216-000-000-000--08--arin.md) | +| `217.0.0.0/8` | RIPE NCC | ALLOCATED | `ripe-ncc` | [record](217-000-000-000--08--ripe-ncc.md) | +| `218.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](218-000-000-000--08--apnic.md) | +| `219.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](219-000-000-000--08--apnic.md) | +| `220.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](220-000-000-000--08--apnic.md) | +| `221.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](221-000-000-000--08--apnic.md) | +| `222.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](222-000-000-000--08--apnic.md) | +| `223.0.0.0/8` | APNIC | ALLOCATED | `apnic` | [record](223-000-000-000--08--apnic.md) | +| `224.0.0.0/8` | Multicast | RESERVED | `iana` | [record](224-000-000-000--08--iana.md) | +| `225.0.0.0/8` | Multicast | RESERVED | `iana` | [record](225-000-000-000--08--iana.md) | +| `226.0.0.0/8` | Multicast | RESERVED | `iana` | [record](226-000-000-000--08--iana.md) | +| `227.0.0.0/8` | Multicast | RESERVED | `iana` | [record](227-000-000-000--08--iana.md) | +| `228.0.0.0/8` | Multicast | RESERVED | `iana` | [record](228-000-000-000--08--iana.md) | +| `229.0.0.0/8` | Multicast | RESERVED | `iana` | [record](229-000-000-000--08--iana.md) | +| `230.0.0.0/8` | Multicast | RESERVED | `iana` | [record](230-000-000-000--08--iana.md) | +| `231.0.0.0/8` | Multicast | RESERVED | `iana` | [record](231-000-000-000--08--iana.md) | +| `232.0.0.0/8` | Multicast | RESERVED | `iana` | [record](232-000-000-000--08--iana.md) | +| `233.0.0.0/8` | Multicast | RESERVED | `iana` | [record](233-000-000-000--08--iana.md) | +| `234.0.0.0/8` | Multicast | RESERVED | `iana` | [record](234-000-000-000--08--iana.md) | +| `235.0.0.0/8` | Multicast | RESERVED | `iana` | [record](235-000-000-000--08--iana.md) | +| `236.0.0.0/8` | Multicast | RESERVED | `iana` | [record](236-000-000-000--08--iana.md) | +| `237.0.0.0/8` | Multicast | RESERVED | `iana` | [record](237-000-000-000--08--iana.md) | +| `238.0.0.0/8` | Multicast | RESERVED | `iana` | [record](238-000-000-000--08--iana.md) | +| `239.0.0.0/8` | Multicast | RESERVED | `iana` | [record](239-000-000-000--08--iana.md) | +| `240.0.0.0/8` | Future use | RESERVED | `iana` | [record](240-000-000-000--08--iana.md) | +| `241.0.0.0/8` | Future use | RESERVED | `iana` | [record](241-000-000-000--08--iana.md) | +| `242.0.0.0/8` | Future use | RESERVED | `iana` | [record](242-000-000-000--08--iana.md) | +| `243.0.0.0/8` | Future use | RESERVED | `iana` | [record](243-000-000-000--08--iana.md) | +| `244.0.0.0/8` | Future use | RESERVED | `iana` | [record](244-000-000-000--08--iana.md) | +| `245.0.0.0/8` | Future use | RESERVED | `iana` | [record](245-000-000-000--08--iana.md) | +| `246.0.0.0/8` | Future use | RESERVED | `iana` | [record](246-000-000-000--08--iana.md) | +| `247.0.0.0/8` | Future use | RESERVED | `iana` | [record](247-000-000-000--08--iana.md) | +| `248.0.0.0/8` | Future use | RESERVED | `iana` | [record](248-000-000-000--08--iana.md) | +| `249.0.0.0/8` | Future use | RESERVED | `iana` | [record](249-000-000-000--08--iana.md) | +| `250.0.0.0/8` | Future use | RESERVED | `iana` | [record](250-000-000-000--08--iana.md) | +| `251.0.0.0/8` | Future use | RESERVED | `iana` | [record](251-000-000-000--08--iana.md) | +| `252.0.0.0/8` | Future use | RESERVED | `iana` | [record](252-000-000-000--08--iana.md) | +| `253.0.0.0/8` | Future use | RESERVED | `iana` | [record](253-000-000-000--08--iana.md) | +| `254.0.0.0/8` | Future use | RESERVED | `iana` | [record](254-000-000-000--08--iana.md) | +| `255.0.0.0/8` | Future use | RESERVED | `iana` | [record](255-000-000-000--08--iana.md) | + +## IANA special-purpose ranges + +Special-purpose prefixes can overlap top-level `/8` records and each other because they express more-specific protocol semantics. + +| Range | Name | Globally reachable | Record | +|---|---|---|---| +| `0.0.0.0/8` | This network | False | [record](000-000-000-000--08--iana.md) | +| `0.0.0.0/32` | This host on this network | False | [record](000-000-000-000--32--iana-special.md) | +| `10.0.0.0/8` | Private-Use | False | [record](010-000-000-000--08--iana-special.md) | +| `100.64.0.0/10` | Shared Address Space | False | [record](100-064-000-000--10--iana-special.md) | +| `127.0.0.0/8` | Loopback | False [1] | [record](127-000-000-000--08--iana-special.md) | +| `169.254.0.0/16` | Link Local | False | [record](169-254-000-000--16--iana-special.md) | +| `172.16.0.0/12` | Private-Use | False | [record](172-016-000-000--12--iana-special.md) | +| `192.0.0.0/24` | IETF Protocol Assignments | False | [record](192-000-000-000--24--iana-special.md) | +| `192.0.0.0/29` | IPv4 Service Continuity Prefix | False | [record](192-000-000-000--29--iana-special.md) | +| `192.0.0.8/32` | IPv4 dummy address | False | [record](192-000-000-008--32--iana-special.md) | +| `192.0.0.9/32` | Port Control Protocol Anycast | True | [record](192-000-000-009--32--iana-special.md) | +| `192.0.0.10/32` | Traversal Using Relays around NAT Anycast | True | [record](192-000-000-010--32--iana-special.md) | +| `192.0.0.170/32` | NAT64/DNS64 Discovery | False | [record](192-000-000-170--32--iana-special.md) | +| `192.0.0.171/32` | NAT64/DNS64 Discovery | False | [record](192-000-000-171--32--iana-special.md) | +| `192.0.2.0/24` | Documentation (TEST-NET-1) | False | [record](192-000-002-000--24--iana-special.md) | +| `192.31.196.0/24` | AS112-v4 | True | [record](192-031-196-000--24--iana-special.md) | +| `192.52.193.0/24` | AMT | True | [record](192-052-193-000--24--iana-special.md) | +| `192.88.99.0/24` | Deprecated (6to4 Relay Anycast) | Not stated | [record](192-088-099-000--24--iana-special.md) | +| `192.88.99.2/32` | 6a44-relay anycast address | False | [record](192-088-099-002--32--iana-special.md) | +| `192.168.0.0/16` | Private-Use | False | [record](192-168-000-000--16--iana-special.md) | +| `192.175.48.0/24` | Direct Delegation AS112 Service | True | [record](192-175-048-000--24--iana-special.md) | +| `198.18.0.0/15` | Benchmarking | False | [record](198-018-000-000--15--iana-special.md) | +| `198.51.100.0/24` | Documentation (TEST-NET-2) | False | [record](198-051-100-000--24--iana-special.md) | +| `203.0.113.0/24` | Documentation (TEST-NET-3) | False | [record](203-000-113-000--24--iana-special.md) | +| `240.0.0.0/4` | Reserved | False | [record](240-000-000-000--04--iana-special.md) | +| `255.255.255.255/32` | Limited Broadcast | False | [record](255-255-255-255--32--iana-special.md) | diff --git a/registry-ips/README.md b/registry-ips/README.md index 96110a1..23e4ca8 100644 --- a/registry-ips/README.md +++ b/registry-ips/README.md @@ -20,9 +20,9 @@ The parts mean: - `zero-padded-network-address`: canonical IPv4 network address, each octet padded to three digits and separated by hyphens; - `zero-padded-prefix-length`: CIDR range number without `/`, padded to two digits; -- `registry-or-status`: authoritative number registry when the range has been researched (`iana`, `afrinic`, `apnic`, `arin`, `lacnic`, or `ripe-ncc`), otherwise `placeholder`. +- `registry-or-status`: authoritative number registry when the exact range has a researched/manual record (`iana`, `afrinic`, `apnic`, `arin`, `lacnic`, or `ripe-ncc`); `iana-special` for generated IANA special-purpose records; otherwise `placeholder`. -A known top-level registry is not enough to put that registry in the suffix. If the exact range's holder, routing, and subdivision have not been investigated, use `placeholder`. +Top-level `/8` records generated from the IANA IPv4 Address Space Registry use their current RDAP authority in the suffix. This is registry-level attribution, not a claim that one entity holds or operates every more-specific address. The zero padding is required because repository browsers sort filenames lexicographically: without it, `1-10...` would appear before `1-2...`. @@ -30,16 +30,34 @@ IPv6 filenames use the same rule, with colons replaced by hyphens and compressed ## Current coverage -| Range | Registry | Classification | Status | Known exact addresses | Record | -|---|---|---|---|---|---| -| `0.0.0.0/8` | IANA | Special-purpose | Researched | `0.0.0.0` | [record](000-000-000-000--08--iana.md) | -| `1.0.0.0/16` | APNIC | Pending subdivision/research | Placeholder | — | [record](001-000-000-000--16--placeholder.md) | -| `1.1.0.0/24` | APNIC | Pending research | Placeholder | — | [record](001-001-000-000--24--placeholder.md) | -| `1.1.1.0/24` | APNIC | Public unicast | Researched | `1.1.1.1` | [record](001-001-001-000--24--apnic.md) | +The generated [complete IPv4 index](IPV4-INDEX.md) now contains: -These four files now provide contiguous documented coverage from `0.0.0.0` through `1.1.1.255`. The two middle files are explicitly marked as placeholders and must not be interpreted as fully researched ownership records. +- all **256 top-level `/8` ranges** from the IANA IPv4 Address Space Registry, providing gapless coverage of the complete IPv4 address space; +- all **26 expanded prefixes** from the IANA IPv4 Special-Purpose Address Registry; +- links to every generated baseline range file, with manually researched records retained alongside them. -This is **not yet a list of all global ranges**. The expansion plan is in [`research/ip-network-roadmap.md`](../research/ip-network-roadmap.md). +The folder currently contains **284 range files**: 280 generated IANA baseline records and four pre-existing manual research/placeholder records. Overlap is intentional: a top-level `/8`, a special-purpose prefix, and a more-specific researched range describe different layers of the same address space. + +Examples of manual detail retained alongside the generated baseline: + +| Range | Registry | Classification | Status | Record | +|---|---|---|---|---| +| `0.0.0.0/8` | IANA | Special-purpose | Researched | [record](000-000-000-000--08--iana.md) | +| `1.0.0.0/16` | APNIC | Pending subdivision/research | Placeholder | [record](001-000-000-000--16--placeholder.md) | +| `1.1.0.0/24` | APNIC | Pending research | Placeholder | [record](001-001-000-000--24--placeholder.md) | +| `1.1.1.0/24` | APNIC | Public unicast | Researched | [record](001-001-001-000--24--apnic.md) | + +This is exhaustive at the IANA top-level `/8` layer, but not yet exhaustive for all more-specific RIR allocations, BGP announcements, operators, services, individual IPv4 addresses, or IPv6. The expansion plan is in [`research/ip-network-roadmap.md`](../research/ip-network-roadmap.md). + +## Synchronization + +Run: + +```text +make sync-iana-ipv4 +``` + +The synchronization script downloads both authoritative IANA CSV registries, verifies that all 256 `/8` blocks are present, expands multi-prefix special-purpose rows, regenerates CSV/index artifacts, and updates only files carrying its generated-file marker. Manually researched files are never overwritten. ## Required contents diff --git a/scripts/sync_iana_ipv4.py b/scripts/sync_iana_ipv4.py new file mode 100644 index 0000000..b27b85e --- /dev/null +++ b/scripts/sync_iana_ipv4.py @@ -0,0 +1,345 @@ +#!/usr/bin/env python3 +"""Synchronize authoritative IANA IPv4 range registries into Markdown and CSV.""" + +from __future__ import annotations + +import argparse +import csv +import io +import re +import urllib.request +from collections import Counter +from datetime import datetime, timezone +from ipaddress import IPv4Network, ip_network +from pathlib import Path + +ROOT = Path(__file__).resolve().parents[1] +RANGE_DIR = ROOT / "registry-ips" +DATA_DIR = ROOT / "data" +GENERATED_MARKER = "" +TOP_LEVEL_URL = "https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.csv" +TOP_LEVEL_SOURCE = "https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml" +SPECIAL_URL = "https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry-1.csv" +SPECIAL_SOURCE = "https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml" +TOP_FIELDS = ["Prefix", "Designation", "Date", "WHOIS", "RDAP", "Status [1]", "Note"] +SPECIAL_FIELDS = [ + "Address Block", "Name", "RFC", "Allocation Date", "Termination Date", + "Source", "Destination", "Forwardable", "Globally Reachable", "Reserved-by-Protocol", +] + + +def top_level_network(value: str) -> IPv4Network: + match = re.fullmatch(r"(\d{3})/8", value.strip()) + if not match: + raise ValueError(f"invalid IANA top-level prefix: {value!r}") + first = int(match.group(1)) + if not 0 <= first <= 255: + raise ValueError(f"invalid first octet: {first}") + return IPv4Network(f"{first}.0.0.0/8") + + +def registry_slug(designation: str, rdap: str) -> str: + value = f"{designation} {rdap}".lower() + if "afrinic" in value: + return "afrinic" + if "apnic" in value: + return "apnic" + if "ripe" in value: + return "ripe-ncc" + if "lacnic" in value: + return "lacnic" + if "arin" in value: + return "arin" + if not rdap.strip() or "iana" in value: + return "iana" + raise ValueError(f"cannot derive registry from designation={designation!r}, rdap={rdap!r}") + + +def clean_rdap(value: str) -> str: + cleaned = value.strip() + boundaries = [position for scheme in ("https://", "http://") if (position := cleaned.find(scheme, 1)) > 0] + return cleaned[:min(boundaries)] if boundaries else cleaned + + +def range_filename(network: IPv4Network, suffix: str) -> str: + octets = "-".join(f"{int(part):03d}" for part in str(network.network_address).split(".")) + return f"{octets}--{network.prefixlen:02d}--{suffix}.md" + + +def expand_address_blocks(value: str) -> list[IPv4Network]: + networks = [] + for part in value.split(","): + cleaned = re.sub(r"\s+\[\d+\]\s*$", "", part.strip()) + parsed = ip_network(cleaned, strict=True) + if not isinstance(parsed, IPv4Network): + raise ValueError(f"not IPv4: {part!r}") + networks.append(parsed) + return networks + + +def parse_top_level_csv(text: str) -> list[dict[str, object]]: + reader = csv.DictReader(io.StringIO(text.lstrip("\ufeff"))) + if reader.fieldnames != TOP_FIELDS: + raise ValueError(f"unexpected top-level columns: {reader.fieldnames!r}") + rows: list[dict[str, object]] = [] + for raw in reader: + network = top_level_network(raw["Prefix"]) + rows.append({**raw, "network": network, "registry": registry_slug(raw["Designation"], raw["RDAP"])}) + networks = {row["network"] for row in rows} + expected = {IPv4Network(f"{first}.0.0.0/8") for first in range(256)} + if len(rows) != 256 or networks != expected: + raise ValueError(f"top-level registry must contain exactly 256 unique /8 ranges; found {len(rows)} rows") + return sorted(rows, key=lambda row: int(row["network"].network_address)) + + +def parse_special_csv(text: str) -> list[dict[str, object]]: + reader = csv.DictReader(io.StringIO(text.lstrip("\ufeff"))) + if reader.fieldnames != SPECIAL_FIELDS: + raise ValueError(f"unexpected special-purpose columns: {reader.fieldnames!r}") + rows: list[dict[str, object]] = [] + for raw in reader: + for network in expand_address_blocks(raw["Address Block"]): + rows.append({**raw, "network": network}) + prefixes = [row["network"] for row in rows] + if len(prefixes) != len(set(prefixes)): + raise ValueError("special-purpose registry contains duplicate expanded prefixes") + return sorted(rows, key=lambda row: (int(row["network"].network_address), row["network"].prefixlen)) + + +def fetch_text(url: str) -> str: + request = urllib.request.Request(url, headers={"User-Agent": "network-v1-registry-sync/1.0"}) + with urllib.request.urlopen(request, timeout=60) as response: + return response.read().decode("utf-8-sig") + + +def write_generated(path: Path, content: str) -> bool: + if path.exists() and GENERATED_MARKER not in path.read_text(encoding="utf-8"): + return False + path.parent.mkdir(parents=True, exist_ok=True) + if path.exists() and path.read_text(encoding="utf-8") == content: + return False + path.write_text(content, encoding="utf-8") + return True + + +def attribution_text(row: dict[str, object]) -> str: + network = row["network"] + designation = str(row["Designation"]).strip() or "not stated" + registry = str(row["registry"]) + status = str(row["Status [1]"]).lower() + if registry == "iana": + return ( + f"IANA records **{network}** as **{designation}** with status **{status}**. " + "It is not presented here as an ordinary allocation with one network operator." + ) + return ( + f"At the top-level `/8` registry layer, IANA designates **{network}** to **{designation}** " + f"and the RDAP authority maps to **{registry}**. This does not identify one holder or operator " + "for every address inside the block; detailed attribution requires more-specific RDAP and BGP research." + ) + + +def render_top_level(row: dict[str, object], checked: str) -> str: + network = row["network"] + registry = str(row["registry"]) + designation = str(row["Designation"]).strip() or "Not stated" + return f"""{GENERATED_MARKER} +# {network} — IANA top-level IPv4 registry + +## Who is this IP range? + +{attribution_text(row)} + +## Registry record + +- **Range:** `{network}` +- **IANA designation:** {designation} +- **Registry suffix:** `{registry}` +- **IANA status:** {row['Status [1]']} +- **Allocation/record date:** {row['Date'] or 'Not stated'} +- **WHOIS authority:** {row['WHOIS'] or 'Not stated'} +- **RDAP authority:** {clean_rdap(str(row['RDAP'])) or 'Not stated'} +- **IANA note:** {row['Note'] or 'None'} +- **Checked:** {checked} + +## Scope and limitations + +This record identifies the authoritative **top-level `/8` disposition**. It does not enumerate the many more-specific allocations, assignments, route origins, operators, services, or exact addresses inside the range. + +A registry designation is not proof of legal ownership, current routing, physical location, or service operation. Use more-specific RDAP, BGP, RPKI, and operator sources before making those claims. + +## Source + +- [IANA IPv4 Address Space registry]({TOP_LEVEL_SOURCE}), checked {checked} +""" + + +def clean_name(value: str) -> str: + return " ".join(value.strip().strip('"').split()) + + +def special_filename(network: IPv4Network) -> str: + if network == IPv4Network("0.0.0.0/8"): + return range_filename(network, "iana") + return range_filename(network, "iana-special") + + +def render_special(row: dict[str, object], checked: str) -> str: + network = row["network"] + name = clean_name(str(row["Name"])) + return f"""{GENERATED_MARKER} +# {network} — {name} + +## Who is this IP range? + +IANA identifies **{network}** as **{name}** special-purpose IPv4 space. This is a protocol or standards classification, not an assertion that one company owns or operates every address in the range. + +## Special-purpose properties + +- **Range:** `{network}` +- **Name:** {name} +- **RFC/reference:** {clean_name(str(row['RFC'])) or 'Not stated'} +- **Allocation date:** {row['Allocation Date'] or 'Not stated'} +- **Termination date:** {row['Termination Date'] or 'Not stated'} +- **Valid as source:** {row['Source'] or 'Not stated'} +- **Valid as destination:** {row['Destination'] or 'Not stated'} +- **Forwardable:** {row['Forwardable'] or 'Not stated'} +- **Globally reachable:** {row['Globally Reachable'] or 'Not stated'} +- **Reserved by protocol:** {row['Reserved-by-Protocol'] or 'Not stated'} +- **Checked:** {checked} + +## Interpretation + +The properties above are copied from the authoritative IANA special-purpose registry. Footnote markers are retained because exceptions and qualifications matter. Routing or operational claims require separate current evidence. + +## Source + +- [IANA IPv4 Special-Purpose Address Registry]({SPECIAL_SOURCE}), checked {checked} +""" + + +def write_csv(path: Path, fieldnames: list[str], rows: list[dict[str, str]]) -> None: + path.parent.mkdir(parents=True, exist_ok=True) + with path.open("w", newline="", encoding="utf-8") as handle: + writer = csv.DictWriter(handle, fieldnames=fieldnames, lineterminator="\n") + writer.writeheader() + writer.writerows(rows) + + +def render_index(top_rows: list[dict[str, object]], special_rows: list[dict[str, object]], checked: str) -> str: + registry_counts = Counter(str(row["registry"]) for row in top_rows) + status_counts = Counter(str(row["Status [1]"]).lower() for row in top_rows) + lines = [ + GENERATED_MARKER, + "# Complete IANA IPv4 range index", + "", + f"Generated from authoritative IANA registries and checked **{checked}**.", + "", + "## Coverage", + "", + f"- **{len(top_rows)} top-level `/8` records**, covering all IPv4 addresses from `0.0.0.0` through `255.255.255.255` without gaps.", + f"- **{len(special_rows)} expanded special-purpose prefixes** from the IANA IPv4 Special-Purpose Address Registry.", + "- More-specific manual research records and placeholders remain alongside these authoritative baselines.", + "", + "## Top-level counts", + "", + "### By RDAP registry authority", + "", + ] + lines.extend(f"- `{name}`: {count}" for name, count in sorted(registry_counts.items())) + lines.extend(["", "### By IANA status", ""]) + lines.extend(f"- `{name}`: {count}" for name, count in sorted(status_counts.items())) + lines.extend([ + "", "## All top-level IPv4 /8 ranges", "", + "| Range | IANA designation | Status | Registry/RDAP | Record |", + "|---|---|---|---|---|", + ]) + for row in top_rows: + network = row["network"] + filename = range_filename(network, str(row["registry"])) + designation = str(row["Designation"]).replace("|", "\\|") + lines.append(f"| `{network}` | {designation} | {row['Status [1]']} | `{row['registry']}` | [record]({filename}) |") + lines.extend([ + "", "## IANA special-purpose ranges", "", + "Special-purpose prefixes can overlap top-level `/8` records and each other because they express more-specific protocol semantics.", + "", "| Range | Name | Globally reachable | Record |", + "|---|---|---|---|", + ]) + for row in special_rows: + network = row["network"] + name = clean_name(str(row["Name"])).replace("|", "\\|") + lines.append(f"| `{network}` | {name} | {row['Globally Reachable'] or 'Not stated'} | [record]({special_filename(network)}) |") + return "\n".join(lines) + "\n" + + +def sync(top_text: str, special_text: str, checked: str) -> tuple[int, int]: + top_rows = parse_top_level_csv(top_text) + special_rows = parse_special_csv(special_text) + expected_generated: set[Path] = set() + + top_csv_rows: list[dict[str, str]] = [] + for row in top_rows: + network = row["network"] + filename = range_filename(network, str(row["registry"])) + path = RANGE_DIR / filename + write_generated(path, render_top_level(row, checked)) + if path.exists() and GENERATED_MARKER in path.read_text(encoding="utf-8"): + expected_generated.add(path) + top_csv_rows.append({ + "prefix": str(network), "designation": str(row["Designation"]), + "registry": str(row["registry"]), "status": str(row["Status [1]"]).lower(), + "allocation_date": str(row["Date"]), "whois": str(row["WHOIS"]), + "rdap": clean_rdap(str(row["RDAP"])), "note": str(row["Note"]), + "source_url": TOP_LEVEL_SOURCE, "verified_at": checked, "filename": filename, + }) + + special_csv_rows: list[dict[str, str]] = [] + for row in special_rows: + network = row["network"] + filename = special_filename(network) + path = RANGE_DIR / filename + write_generated(path, render_special(row, checked)) + if path.exists() and GENERATED_MARKER in path.read_text(encoding="utf-8"): + expected_generated.add(path) + special_csv_rows.append({ + "prefix": str(network), "name": clean_name(str(row["Name"])), "rfc": clean_name(str(row["RFC"])), + "allocation_date": str(row["Allocation Date"]), "termination_date": str(row["Termination Date"]), + "source": str(row["Source"]), "destination": str(row["Destination"]), + "forwardable": str(row["Forwardable"]), "globally_reachable": str(row["Globally Reachable"]), + "reserved_by_protocol": str(row["Reserved-by-Protocol"]), "source_url": SPECIAL_SOURCE, + "verified_at": checked, "filename": filename, + }) + + for path in RANGE_DIR.glob("*.md"): + if path not in expected_generated and path.name != "IPV4-INDEX.md" and GENERATED_MARKER in path.read_text(encoding="utf-8"): + path.unlink() + + write_csv( + DATA_DIR / "iana-ipv4-top-level-ranges.csv", + ["prefix", "designation", "registry", "status", "allocation_date", "whois", "rdap", "note", "source_url", "verified_at", "filename"], + top_csv_rows, + ) + write_csv( + DATA_DIR / "iana-ipv4-special-ranges.csv", + ["prefix", "name", "rfc", "allocation_date", "termination_date", "source", "destination", "forwardable", "globally_reachable", "reserved_by_protocol", "source_url", "verified_at", "filename"], + special_csv_rows, + ) + (RANGE_DIR / "IPV4-INDEX.md").write_text(render_index(top_rows, special_rows, checked), encoding="utf-8") + return len(top_rows), len(special_rows) + + +def main() -> int: + parser = argparse.ArgumentParser() + parser.add_argument("--top-level-file", type=Path) + parser.add_argument("--special-file", type=Path) + parser.add_argument("--checked", default=datetime.now(timezone.utc).date().isoformat()) + args = parser.parse_args() + top_text = args.top_level_file.read_text(encoding="utf-8-sig") if args.top_level_file else fetch_text(TOP_LEVEL_URL) + special_text = args.special_file.read_text(encoding="utf-8-sig") if args.special_file else fetch_text(SPECIAL_URL) + top_count, special_count = sync(top_text, special_text, args.checked) + print(f"Synchronized {top_count} top-level IPv4 ranges and {special_count} special-purpose prefixes.") + return 0 + + +if __name__ == "__main__": + raise SystemExit(main()) diff --git a/scripts/validate.py b/scripts/validate.py index d2b0226..85cf2ba 100644 --- a/scripts/validate.py +++ b/scripts/validate.py @@ -123,6 +123,10 @@ def main() -> int: ROOT / "docs" / "04-ip-address-model.md", ROOT / "registry-ips" / "README.md", ROOT / "registry-ips" / "TEMPLATE.md", + ROOT / "registry-ips" / "IPV4-INDEX.md", + ROOT / "data" / "iana-ipv4-top-level-ranges.csv", + ROOT / "data" / "iana-ipv4-special-ranges.csv", + ROOT / "scripts" / "sync_iana_ipv4.py", ROOT / "registry-ips" / "000-000-000-000--08--iana.md", ROOT / "registry-ips" / "001-000-000-000--16--placeholder.md", ROOT / "registry-ips" / "001-001-000-000--24--placeholder.md", @@ -135,7 +139,7 @@ def main() -> int: range_records = sorted((ROOT / "registry-ips").glob("*.md")) for path in range_records: - if path.name in {"README.md", "TEMPLATE.md"}: + if path.name in {"README.md", "TEMPLATE.md", "IPV4-INDEX.md"}: continue headings = [line.strip() for line in path.read_text(encoding="utf-8").splitlines() if line.startswith("## ")] if not headings or headings[0] != "## Who is this IP range?": diff --git a/tests/test_sync_iana_ipv4.py b/tests/test_sync_iana_ipv4.py new file mode 100644 index 0000000..891c8c8 --- /dev/null +++ b/tests/test_sync_iana_ipv4.py @@ -0,0 +1,121 @@ +from __future__ import annotations + +import csv +import importlib.util +import io +import tempfile +import unittest +from ipaddress import IPv4Network +from pathlib import Path + +ROOT = Path(__file__).resolve().parents[1] +MODULE_PATH = ROOT / "scripts" / "sync_iana_ipv4.py" + + +def load_module(): + spec = importlib.util.spec_from_file_location("sync_iana_ipv4", MODULE_PATH) + if spec is None or spec.loader is None: + raise RuntimeError("cannot load sync_iana_ipv4") + module = importlib.util.module_from_spec(spec) + spec.loader.exec_module(module) + return module + + +class SyncIanaIPv4Tests(unittest.TestCase): + @classmethod + def setUpClass(cls): + cls.sync = load_module() + + def test_top_level_prefix_is_normalized(self): + self.assertEqual( + self.sync.top_level_network("001/8"), + IPv4Network("1.0.0.0/8"), + ) + + def test_registry_slug_uses_rdap_authority(self): + self.assertEqual( + self.sync.registry_slug("APNIC", "https://rdap.apnic.net/"), + "apnic", + ) + self.assertEqual( + self.sync.registry_slug( + "Legacy allocation", + "https://rdap.arin.net/registryhttp://rdap.arin.net/registry", + ), + "arin", + ) + self.assertEqual(self.sync.registry_slug("IANA - Reserved", ""), "iana") + + def test_rdap_url_concatenation_is_normalized(self): + self.assertEqual( + self.sync.clean_rdap("https://rdap.arin.net/registryhttp://rdap.arin.net/registry"), + "https://rdap.arin.net/registry", + ) + self.assertEqual(self.sync.clean_rdap("https://rdap.apnic.net/"), "https://rdap.apnic.net/") + + def test_filename_sorts_numerically_in_lexical_order(self): + self.assertEqual( + self.sync.range_filename(IPv4Network("1.2.3.0/24"), "apnic"), + "001-002-003-000--24--apnic.md", + ) + + def test_multiple_special_blocks_are_expanded(self): + self.assertEqual( + self.sync.expand_address_blocks("192.0.0.170/32, 192.0.0.171/32"), + [IPv4Network("192.0.0.170/32"), IPv4Network("192.0.0.171/32")], + ) + + def test_special_block_footnote_is_ignored_for_parsing(self): + self.assertEqual( + self.sync.expand_address_blocks("192.0.0.0/24 [2]"), + [IPv4Network("192.0.0.0/24")], + ) + + def test_source_text_whitespace_is_normalized(self): + self.assertEqual(self.sync.clean_name('"[RFC8190]\n [RFC919], Section 7"'), "[RFC8190] [RFC919], Section 7") + + def test_parse_top_level_requires_complete_ipv4_coverage(self): + output = io.StringIO() + writer = csv.DictWriter( + output, + fieldnames=["Prefix", "Designation", "Date", "WHOIS", "RDAP", "Status [1]", "Note"], + ) + writer.writeheader() + for first in range(256): + writer.writerow({ + "Prefix": f"{first:03d}/8", + "Designation": "Example", + "Date": "2026-01", + "WHOIS": "", + "RDAP": "", + "Status [1]": "RESERVED", + "Note": "", + }) + rows = self.sync.parse_top_level_csv(output.getvalue()) + self.assertEqual(len(rows), 256) + self.assertEqual(rows[0]["network"], IPv4Network("0.0.0.0/8")) + self.assertEqual(rows[-1]["network"], IPv4Network("255.0.0.0/8")) + + def test_parse_top_level_rejects_missing_slash_eight(self): + sample = "Prefix,Designation,Date,WHOIS,RDAP,Status [1],Note\n000/8,IANA,1981-09,,,RESERVED,\n" + with self.assertRaisesRegex(ValueError, "256"): + self.sync.parse_top_level_csv(sample) + + def test_manual_range_file_is_not_overwritten(self): + with tempfile.TemporaryDirectory() as temporary: + directory = Path(temporary) + path = directory / "001-000-000-000--08--apnic.md" + path.write_text("# hand researched\n", encoding="utf-8") + changed = self.sync.write_generated(path, "# generated\n") + self.assertFalse(changed) + self.assertEqual(path.read_text(encoding="utf-8"), "# hand researched\n") + + def test_generated_csv_uses_lf_line_endings(self): + with tempfile.TemporaryDirectory() as temporary: + path = Path(temporary) / "ranges.csv" + self.sync.write_csv(path, ["prefix"], [{"prefix": "1.0.0.0/8"}]) + self.assertNotIn(b"\r", path.read_bytes()) + + +if __name__ == "__main__": + unittest.main()