Hostname
cottonclassics.de
Last fetched
cottonclassics.de resolves to 104.26.12.217, announced in 104.28.23.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. cottonclassics.de is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.26.12.217
104.28.23.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.13.217
104.28.23.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.71.10
172.68.26.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for cottonclassics.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| preview.cottonclassics.de |
| stage.cottonclassics.de |
| staging.cottonclassics.de |
| test.cottonclassics.de |
| www.cottonclassics.de |
Showing 5 of 5 subdomains (5 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- aspen.ns.cloudflare.com
- jaime.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- cottonclassics-de.mail.protection.outlook.com
SPF policy
- a: mail.cotton.at
- include: spf.protection.outlook.com
- mx: cottonclassics.de
- ip: 185.93.214.100
- ip: 185.93.214.101
- ip: 185.93.214.102
Threat-feed evidence
History
Related pages
Pivot from cottonclassics.de into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "cottonclassics.de"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.