Country
—
ASN LANDING PAGE
SUEC-DACOR-AS - suec // dacor GmbH
Last updated · Apr 4, 2026
Country
—
Total prefixes
19
IPv4 prefixes
13
IPv6 prefixes
6
SUEC-DACOR-AS - suec // dacor GmbH currently shows 19 prefixes and 49 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.
SUEC-DACOR-AS - suec // dacor GmbH 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.
AS33891
AS33891
—
AS3320
AS3320
—
AS6939
AS6939
—
AS9002
AS9002
—
AS3214
AS3214
—
AS13030
AS13030
—
AS34549
AS34549
—
AS35625
AS35625
—
AS5405
AS5405
—
AS34019
AS34019
—
AS20764
AS20764
—
AS35280
AS35280
—
AS48362
AS48362
—
AS29632
AS29632
—
AS34927
AS34927
—
AS6057
AS6057
—
AS34177
AS34177
—
AS137409
AS137409
—
AS8298
AS8298
—
AS29075
AS29075
—
AS29691
AS29691
—
AS680
AS680
—
AS37100
AS37100
—
AS37468
AS37468
—
AS41327
AS41327
—
AS12779
AS12779
—
AS39351
AS39351
—
AS52320
AS52320
—
AS25091
AS25091
—
AS8218
AS8218
—
AS8220
AS8220
—
AS8758
AS8758
—
AS14840
AS14840
—
AS21412
AS21412
—
AS25220
AS25220
—
AS30781
AS30781
—
AS35360
AS35360
—
AS51185
AS51185
—
AS206356
AS206356
—
AS210937
AS210937
—
| Prefix | Name | Country |
|---|---|---|
| 176.52.192.0/21 | AS28876 | — |
| 185.53.216.0/22 | AS28876 | — |
| 217.24.48.0/20 | AS28876 | — |
| 217.24.48.0/21 | AS28876 | — |
| 217.24.56.0/21 | AS28876 | — |
| 2a00:9d80:8000::/33 | AS28876 | — |
| 2a00:9d80::/32 | AS28876 | — |
| 2a00:9d80::/33 | AS28876 | — |
| 2a00:9d81:8000::/33 | AS28876 | — |
| 2a00:9d81::/32 | AS28876 | — |
| 2a00:9d81::/33 | AS28876 | — |
| 37.61.128.0/20 | AS28876 | — |
| 5.100.0.0/18 | AS28876 | — |
| 5.100.0.0/19 | AS28876 | — |
| 5.100.0.0/24 | AS28876 | — |
| 5.100.32.0/19 | AS28876 | — |
| 81.89.160.0/20 | AS28876 | — |
| 81.89.160.0/21 | AS28876 | — |
| 81.89.168.0/21 | AS28876 | — |
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.
AS28876 is an autonomous system number used to identify an independently operated network. The current page associates it with SUEC-DACOR-AS - suec // dacor GmbH 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 AS28876. 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 AS28876, 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.