Skip to content

Hostname

tudock.de

Last fetched

tudock.de resolves to 185.233.55.137, announced in 185.233.52.0/22 by MITTWALD-AS - Robert Meyer trading as "Mittwald CM Service GmbH & Co. KG" in DE. tudock.de is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · tudock.deRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/tudock.de

Resolution chain

IPv6 resolution

No AAAA record for tudock.de is recorded in WhisperGraph.

Attribution

robert meyer trading mittwald cm

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for tudock.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
auswertung.tudock.de
blog.tudock.de
data.tudock.de
insights.tudock.de
lichtakademie.tudock.de
search-insights.tudock.de
stage.tudock.de
www.tudock.de

Showing 8 of 9. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • ns01.agenturserver.co
  • ns01.agenturserver.de
  • ns01.agenturserver.it

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: spf.crsend.com
  • include: _spf.google.com
  • include: agenturserver.de
  • a: srv-a-de.c-503.maxcluster.net

Threat-feed evidence

History

Related pages

Pivot from tudock.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: "tudock.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.