Skip to content

Hostname

aignermunich.de

Last fetched

aignermunich.de resolves to 104.20.18.110, announced in 104.20.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. aignermunich.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 · aignermunich.deRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/aignermunich.de

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for aignermunich.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
backend.aignermunich.de
dev-backend.aignermunich.de
dev-pim.aignermunich.de
dev.aignermunich.de
feature-backend.aignermunich.de
ihtmci.aignermunich.de
integration.aignermunich.de
old.aignermunich.de
pim.aignermunich.de
retail.aignermunich.de
search-dev.aignermunich.de
search.aignermunich.de

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

Mail and authentication

Nameservers

  • dave.ns.cloudflare.com
  • molly.ns.cloudflare.com

MX records

  • mail.aignermunich.com

SPF policy

  • include: emsd1.com
  • include: emsmtp.com
  • mx: aignermunich.de
  • include: spf.maxcluster.de
  • ip: 149.233.1.214
  • ip: 62.113.230.113
  • ip: 62.113.230.96

Threat-feed evidence

History

Related pages

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