Hostname
teekanne.de
Last fetched
teekanne.de resolves to 68.183.240.83, announced in 68.183.240.0/22 by DIGITALOCEAN-ASN - DigitalOcean, LLC in DE. teekanne.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
- 68.183.240.83
68.183.240.0/22 · DIGITALOCEAN-ASN - DigitalOcean, LLC · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for teekanne.de is recorded in WhisperGraph.
Attribution
digitalocean
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for teekanne.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
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
- ns1.dnsdienst.de
- ns2.dnsdienst.de
- ns3.dnsdienst.de
MX records
- teekanne-de.mail.protection.outlook.com
SPF policy
- ip: 3.214.204.181/32
- ip: 144.76.32.198/32
- ip: 144.76.32.199/32
- ip: 52.178.135.21/32
- ip: 20.107.242.47/32
- ip: 52.60.189.48/32
- ip: 52.17.62.50/32
- ip: 3.105.224.60/32
- include: spf.emailsignatures365.com
- include: spf.imc-hosting.com
- include: spf.mandrillapp.com
- include: spf.protection.outlook.com
- include: _spf.retarus.com
- include: _spf.jpberlin.de
- include: servers.mcsv.net
- include: _spf.mailgun.org
- ip: 141.193.32.4
- ip: 178.15.148.2
- ip: 178.208.97.240
- ip: 194.180.136.18
- ip: 194.180.136.4
- ip: 4.231.171.210
- ip: 4.231.234.136
Threat-feed evidence
History
Related pages
Pivot from teekanne.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: "teekanne.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.