Skip to content

Hostname

ykm.de

Last fetched

ykm.de resolves to 162.55.82.84, announced in 162.55.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. ykm.de is listed by 4 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 4 threat feeds. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
4
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:31 GMT
Last seen on a feed
Wed, 23 Sep 2026 00:28:35 GMT

Nutrition Label

WHISPER CANON · ykm.deRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings5.4/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/ykm.de

Resolution chain

IPv6 resolution

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

Attribution

hetzner

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for ykm.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
2e18c9a6f7d0.ykm.de
beta.ykm.de
beta2.ykm.de
dc-74a54eedeaa2.ykm.de
mail.ykm.de
wurlie.ykm.de
www.ykm.de

Showing 7 of 8. 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

  • rajeev.ns.cloudflare.com
  • vida.ns.cloudflare.com
  • dns.dns1.de
  • dns.dns2.de
  • dns.dns3.de
  • dns.dns4.de

MX records

  • mail.defrax1.de

SPF policy

  • a: ykm.de
  • mx: ykm.de
  • include: mail.ykm.de

Threat-feed evidence

History

Related pages

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