Skip to content

Hostname

irmscher.de

Last fetched

irmscher.de resolves to 212.71.215.200, announced in 212.71.192.0/19 by NEPUSTILNET-AS01 - Dr.-Ing. Nepustil & Co. GmbH Internet Service Center Ingenieurgesellschaft fuer Systemsoftware und Kommunikationstechnik in DE. irmscher.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 · irmscher.deRouting diversity1.5/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/irmscher.de

Resolution chain

IPv6 resolution

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

Attribution

dr ing nepustil center ingenieurgesellschaft fuer systemsoftware und kommunikationstechnik

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for irmscher.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
email.irmscher.de
email2.irmscher.de
portal.irmscher.de
srv-mail.irmscher.de
test.irmscher.de
www.irmscher.de

Showing 6 of 6 subdomains (6 per page).

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

  • ns.nepustil.com
  • ns1.nepustil.net

MX records

  • email.irmscher.de
  • email2.irmscher.de

SPF policy

  • a: irmscher.de
  • mx: irmscher.de
  • ip: 2001:14f8:1:1:0:0:0:15
  • ip: 212.71.205.21
  • ip: 217.6.123.234
  • ip: 217.92.72.70
  • ip: 2a01:1e8:3:2:0:0:0:1c
  • ip: 2a02:2479:48:3600:0:0:0:1
  • ip: 85.215.78.212
  • ip: 85.236.195.28

Threat-feed evidence

History

Related pages

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