Skip to content

Hostname

meckenheim.de

Last fetched

meckenheim.de resolves to 213.178.85.20, announced in 213.178.64.0/19 by TNG-AS - TNG Stadtnetz GmbH in DE. meckenheim.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 · meckenheim.deRouting diversity1.5/10Peering density7.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/meckenheim.de

Resolution chain

IPv6 resolution

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

Attribution

tng stadtnetz

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for meckenheim.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
bis.meckenheim.de
bkp.meckenheim.de
geoportal.meckenheim.de
intern-geoportal.meckenheim.de
intranet.meckenheim.de
jugend.meckenheim.de
jugendrat.meckenheim.de
kag.meckenheim.de
karriere.meckenheim.de
kgs.meckenheim.de
session.meckenheim.de
session1.meckenheim.de

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

  • dns-relaix.regioit-aachen.de
  • dns01.regioit-aachen.de

MX records

  • gw11.civitec.de
  • gw12.civitec.de

SPF policy

  • ip: 195.243.56.0/24
  • ip: 195.243.129.128/26
  • mx: meckenheim.de
  • include: spf.regioit.de

Threat-feed evidence

History

Related pages

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