Country
—
ASN LANDING PAGE
DNIC-AS-00668 - United States Department of Defense DoD
Last updated · Apr 4, 2026
Country
—
Total prefixes
189
IPv4 prefixes
187
IPv6 prefixes
2
DNIC-AS-00668 - United States Department of Defense DoD currently shows 189 prefixes and 39 upstream, downstream, or peer relationships. Larger prefix inventories often indicate broader network footprint, but they should still be read together with country and peering context.
ASN landing pages are more useful than a single IP page when you want cloud provider attribution, routing research, infrastructure comparison, or network topology analysis at the organization level.
DNIC-AS-00668 - United States Department of Defense DoD is currently associated with an unknown region. Country data is only a starting point; the more important signals are the organization name, website, prefix volume, and peering relationships that reveal whether the network behaves like a cloud platform, ISP, CDN, or enterprise backbone.
This page is currently showing live ASN data that can be used for peer, prefix, and network scale analysis. The most useful next step is usually to return to a related IP landing page, then compare that concrete address with this ASN profile and with broader topic pages for routing, cloud attribution, or WHOIS ownership analysis.
Detailed data for this ASN is not available right now.
AS687
AS687
—
AS13
AS13
—
AS5957
AS5957
—
AS252
AS252
—
AS289
AS289
—
AS22
AS22
—
AS518
AS518
—
AS37
AS37
—
AS6009
AS6009
—
AS84
AS84
—
AS5058
AS5058
—
AS48
AS48
—
AS228
AS228
—
AS213
AS213
—
AS121
AS121
—
AS89
AS89
—
AS5978
AS5978
—
AS393399
AS393399
—
AS2621
AS2621
—
AS1508
AS1508
—
AS4221
AS4221
—
AS5132
AS5132
—
AS366
AS366
—
AS5887
AS5887
—
AS5980
AS5980
—
AS6043
AS6043
—
AS3381
AS3381
—
| Prefix | Name | Country |
|---|---|---|
| 128.132.0.0/16 | AS668 | — |
| 128.160.0.0/17 | AS668 | — |
| 129.229.0.0/16 | AS668 | — |
| 129.92.0.0/16 | AS668 | — |
| 130.109.0.0/16 | AS668 | — |
| 130.163.0.0/16 | AS668 | — |
| 131.120.0.0/16 | AS668 | — |
| 131.121.0.0/16 | AS668 | — |
| 131.122.0.0/16 | AS668 | — |
| 131.214.0.0/16 | AS668 | — |
| 131.218.0.0/16 | AS668 | — |
| 131.250.0.0/17 | AS668 | — |
| 131.250.128.0/18 | AS668 | — |
| 131.250.192.0/20 | AS668 | — |
| 131.92.131.0/24 | AS668 | — |
| 131.92.132.0/22 | AS668 | — |
| 131.92.136.0/21 | AS668 | — |
| 131.92.144.0/21 | AS668 | — |
| 131.92.162.0/23 | AS668 | — |
| 131.92.164.0/22 | AS668 | — |
| 131.92.168.0/21 | AS668 | — |
| 131.92.176.0/22 | AS668 | — |
| 131.92.180.0/23 | AS668 | — |
| 131.92.182.0/23 | AS668 | — |
| 131.92.184.0/23 | AS668 | — |
| 131.92.186.0/24 | AS668 | — |
| 131.92.192.0/18 | AS668 | — |
| 132.193.0.0/16 | AS668 | — |
| 132.45.0.0/16 | AS668 | — |
| 134.164.220.0/24 | AS668 | — |
| 134.166.0.0/18 | AS668 | — |
| 134.166.128.0/22 | AS668 | — |
| 134.166.132.0/23 | AS668 | — |
| 134.166.134.0/24 | AS668 | — |
| 134.166.135.0/24 | AS668 | — |
| 134.166.136.0/23 | AS668 | — |
| 134.166.138.0/24 | AS668 | — |
| 134.166.144.0/20 | AS668 | — |
| 134.166.64.0/18 | AS668 | — |
| 137.128.0.0/16 | AS668 | — |
A strong reference ASN for Google DNS, Google Cloud, and global network footprint analysis.
Useful for analyzing CDN, Anycast, WAF, and large-scale edge network behavior.
Helpful when comparing Azure, enterprise backbone, and large-cloud routing patterns.
A useful ASN landing page for understanding AWS and large cloud-network ownership.
Continue from this ASN into the differences between WHOIS ownership and ASN ownership.
Continue from this ASN into route troubleshooting and network analysis.
Useful when you want to compare this ASN against larger cloud and edge networks.
Continue from the ASN page into WHOIS and ownership verification.
AS668 is an autonomous system number used to identify an independently operated network. The current page associates it with DNIC-AS-00668 - United States Department of Defense DoD in an unknown region, which helps determine whether it behaves like a cloud provider, ISP, CDN, or enterprise backbone.
They help explain the scale, interconnection depth, and route structure of AS668. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
The best next step is usually to return to a concrete IP landing page to see how a specific address maps into AS668, then continue into cloud, WHOIS, or routing topic pages to understand the network in a broader context.
Understand why WHOIS ownership and ASN ownership can differ, and how to combine both when deciding who really owns or operates an IP.
Use WHOIS, ASN, prefixes, and organization data to determine who ultimately owns an IP, range, or resolved domain target.
Learn what ASN, BGP routes, prefixes, upstreams, downstreams, and peers mean, then explore real ASN pages.
Compare large cloud and edge networks such as Google, Cloudflare, Microsoft, and Amazon through their ASN landing pages.