Skip to content

Hostname

tkrz.de

Last fetched

tkrz.de resolves to 185.124.233.193, announced in 185.124.232.0/22 by AS-TKRZ - TKRZ Stadtwerke GmbH in DE. tkrz.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 · tkrz.deRouting diversity1.5/10Peering density7.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/tkrz.de

Resolution chain

IPv6 resolution

Attribution

tkrz stadtwerke

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for tkrz.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
adr-api.tkrz.de
adressen.tkrz.de
autodiscover.tkrz.de
bb.tkrz.de
bestellen.tkrz.de
cloud.tkrz.de
cloudmail.tkrz.de
controlboard.tkrz.de
cust.tkrz.de
dmo1.tkrz.de
dnsweb.tkrz.de
ems2.tkrz.de

Showing 12 of 84. 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

  • ns0.tkrz.de
  • ns1.tkrz.de
  • ns2.tkrz.de
  • ns3.tkrz.de
  • ns4.tkrz.de

MX records

  • fw01.tkrz.de

SPF policy

  • ip: 185.39.85.56/32
  • include: spf.protection.outlook.com
  • include: 5pf.cows-server.de
  • a: fw01.tkrz.de
  • include: spf.emailsys.net
  • ip: 185.64.168.28
  • ip: 2a01:4f8:222:a07:0:0:0:2
  • ip: 2a02:f08:b00b:1000:0:0:0:2
  • ip: 46.182.148.120
  • ip: 89.251.128.37
  • ip: 89.251.128.97
  • ip: 89.251.128.98

Threat-feed evidence

History

Related pages

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