Country
—
ASN LANDING PAGE
SMISHCRAFT - Adam Goodenough
Last updated · Apr 4, 2026
Country
—
Total prefixes
26
IPv4 prefixes
8
IPv6 prefixes
18
SMISHCRAFT - Adam Goodenough currently shows 26 prefixes and 44 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.
SMISHCRAFT - Adam Goodenough 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.
AS34927
AS34927
—
AS6939
AS6939
—
AS52025
AS52025
—
AS208453
AS208453
—
AS835
AS835
—
AS41051
AS41051
—
AS37988
AS37988
—
AS61138
AS61138
—
AS25091
AS25091
—
AS8218
AS8218
—
AS12186
AS12186
—
AS8298
AS8298
—
AS34019
AS34019
—
AS24482
AS24482
—
AS25220
AS25220
—
AS35280
AS35280
—
AS50304
AS50304
—
AS50763
AS50763
—
AS51184
AS51184
—
AS57821
AS57821
—
AS58057
AS58057
—
AS210633
AS210633
—
AS917
AS917
—
AS3216
AS3216
—
AS5405
AS5405
—
AS6057
AS6057
—
AS14840
AS14840
—
AS20764
AS20764
—
AS25160
AS25160
—
AS31122
AS31122
—
AS31742
AS31742
—
AS34177
AS34177
—
AS34549
AS34549
—
AS35266
AS35266
—
AS36236
AS36236
—
AS39122
AS39122
—
AS39351
AS39351
—
AS48362
AS48362
—
AS49544
AS49544
—
AS50300
AS50300
—
| Prefix | Name | Country |
|---|---|---|
| 151.241.74.0/24 | AS210667 | — |
| 168.222.240.0/24 | AS210667 | — |
| 192.67.34.0/24 | AS210667 | — |
| 204.10.192.0/24 | AS210667 | — |
| 2602:fa9b:c0::/48 | AS210667 | — |
| 2a07:54c2:b00b::/48 | AS210667 | — |
| 2a0a:6040:5101::/48 | AS210667 | — |
| 2a0a:6040:5102::/48 | AS210667 | — |
| 2a0a:6040:5103::/48 | AS210667 | — |
| 2a0a:6040:5106::/48 | AS210667 | — |
| 2a0a:6040:5107::/48 | AS210667 | — |
| 2a0a:6040:6101::/48 | AS210667 | — |
| 2a0a:6040:6102::/48 | AS210667 | — |
| 2a0a:6040:6104::/48 | AS210667 | — |
| 2a0a:6040:7101::/48 | AS210667 | — |
| 2a0a:6040:7102::/48 | AS210667 | — |
| 2a0a:6040:7105::/48 | AS210667 | — |
| 2a0e:97c0:a41::/48 | AS210667 | — |
| 2a0e:97c0:a42::/48 | AS210667 | — |
| 2a0e:97c0:a43::/48 | AS210667 | — |
| 2a0e:97c0:a47::/48 | AS210667 | — |
| 2a0e:b107:1788::/48 | AS210667 | — |
| 44.31.238.0/24 | AS210667 | — |
| 44.31.80.0/24 | AS210667 | — |
| 64.49.14.0/24 | AS210667 | — |
| 89.39.211.0/24 | AS210667 | — |
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.
AS210667 is an autonomous system number used to identify an independently operated network. The current page associates it with SMISHCRAFT - Adam Goodenough 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 AS210667. 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 AS210667, 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.