Skip to content

Hostname

4.dating

Last fetched

4.dating resolves to 18.200.136.130, announced in 18.200.0.0/16 by AMAZON-02 - Amazon.com, Inc. in IE. 4.dating 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 · 4.datingRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/4.dating

Resolution chain

IPv6 resolution

No AAAA record for 4.dating is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1408
Registrant organisation
domains by proxy,
Contact emails
4.dating@domainsbyproxy.com, ticket5645698.60@ideolabs.de, do-not-use@privacy-protected.email

Subdomains

Subdomain
wildcard.4.dating
wwa.4.dating
wwv.4.dating
www.4.dating

Showing 4 of 4 subdomains (4 per page).

Mail and authentication

Nameservers

  • ns-19.awsdns-02.com
  • ns-596.awsdns-10.net
  • ns-1090.awsdns-08.org
  • ns-1626.awsdns-11.co.uk

MX records

  • mxb.d.i.e.gmbh

SPF policy

  • include: spf.https-dns.com
  • mx: 4.dating

Threat-feed evidence

History

Related pages

Pivot from 4.dating 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: "4.dating"})-[: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.