Hostname
redcoon.de
Last fetched
redcoon.de resolves to 34.141.222.150, announced in 34.141.208.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in NL. redcoon.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
- 34.141.222.150
34.141.208.0/20 · GOOGLE-CLOUD-PLATFORM - Google LLC · Groningen, NL
- 34.36.160.137
34.32.0.0/11 · GOOGLE-CLOUD-PLATFORM - Google LLC · Kansas City, US
IPv6 resolution
No AAAA record for redcoon.de is recorded in WhisperGraph.
Attribution
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for redcoon.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 |
|---|
| blog.redcoon.de |
| delivery.redcoon.de |
| geburtstag.redcoon.de |
| goldenechili.redcoon.de |
| m.redcoon.de |
| mail.redcoon.de |
| pop3.redcoon.de |
| smtp.redcoon.de |
| tarife.redcoon.de |
| test.redcoon.de |
Showing 10 of 10 subdomains (10 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.
Mail and authentication
Nameservers
- ns1.mediamarktsaturn.com
- a1-250.akam.net
- a10-67.akam.net
- a18-64.akam.net
- a4-65.akam.net
- a5-66.akam.net
- a9-67.akam.net
- 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
- redcoon-de.mail.protection.outlook.com
SPF policy
- include: msh._spf.media-saturn.com
- include: oraclern._spf.media-saturn.com
Threat-feed evidence
History
Related pages
Pivot from redcoon.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: "redcoon.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.