Skip to content

Hostname

jdating.de

Last fetched

jdating.de resolves to 108.131.199.185, announced in 108.138.48.0/21 by AMAZON-02 - Amazon.com, Inc. in IE. jdating.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 · jdating.deRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/jdating.de

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for jdating.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
wildcard.jdating.de
wwc.jdating.de
wwv.jdating.de

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns-50.awsdns-06.com
  • ns-1001.awsdns-61.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
  • ns-1116.awsdns-11.org
  • ns-1612.awsdns-09.co.uk

MX records

  • mxb.d.i.e.gmbh

SPF policy

  • a: mx01.httpsmx.com
  • a: mx02.httpsmx.com
  • a: mx03.httpsmx.com
  • a: mx.mx01dns.com
  • a: mx01.mx01dns.com
  • a: mx02.mx01dns.com
  • a: mx03.mx01dns.com
  • a: mx04.mx01dns.com
  • a: mx05.mx01dns.com
  • mx: jdating.de

Threat-feed evidence

History

Related pages

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