Skip to content

Hostname

herder-ing.de

Last fetched

herder-ing.de is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. herder-ing.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 · herder-ing.deRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/herder-ing.de

Resolution chain

No IPv4 resolution is recorded for herder-ing.de in WhisperGraph.

IPv6 resolution

No AAAA record for herder-ing.de is recorded in WhisperGraph.

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for herder-ing.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
autodiscover.herder-ing.de
cloud.herder-ing.de
extern.herder-ing.de
imap.herder-ing.de
intern.herder-ing.de
mail.herder-ing.de
smtp.herder-ing.de
www.herder-ing.de

Showing 8 of 12. View all subdomains →

Mail and authentication

Nameservers

  • root-dns.netcup.net
  • second-dns.netcup.net
  • third-dns.netcup.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • smtp.herder-ing.de

SPF policy

  • ip: 188.40.239.200/29
  • ip: 2a01:4f8:151:7900::/64
  • a: herder-ing.de
  • mx: herder-ing.de
  • a: smtp.herder-ing.de

Threat-feed evidence

History

Related pages

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