Skip to content

Hostname

apd-hp.de

Last fetched

apd-hp.de resolves to 212.184.206.201, announced in 212.189.8.0/24 by DTAG - Deutsche Telekom AG in DE. apd-hp.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 · apd-hp.deRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.5/10canon.whisper.security/host/apd-hp.de

Resolution chain

IPv6 resolution

Attribution

dtag deutsche telekom

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for apd-hp.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
apd-server.apd-hp.de
corert.apd-hp.de
crusher.apd-hp.de
fserv2.apd-hp.de
mail.apd-hp.de
ns1.apd-hp.de
ns2.apd-hp.de
w2k12-dc-fserv-ca.apd-hp.de
w2k12-dc-fserv.apd-hp.de
w2k12-dc-fserv2.apd-hp.de
w2k12-dc-ns1-ca.apd-hp.de
w2k12-dc-ns1.apd-hp.de

Showing 12 of 18. View all subdomains →

Mail and authentication

Nameservers

  • fserv2.apd-hp.de
  • ns1.apd-hp.de
  • ns2.apd-hp.de
  • pns.dtag.de
  • secondary004.dtag.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

  • mail.apd-hp.de

SPF policy

  • ip: 80.148.45.1/23
  • ip: 62.153.113.1/24
  • ip: 212.184.206.195/26
  • a: apd-hp.de
  • a: corert.apd-hp.de
  • a: crusher.apd-hp.de
  • a: mail.apd-it.eu
  • ip: 2003:58:a074:0:211:85ff:fee7:73a3
  • ip: 62.153.56.90

Threat-feed evidence

History

Related pages

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