Skip to content

Hostname

userdatatrust.com

Last fetched

userdatatrust.com resolves to 18.197.47.197, announced in 18.196.0.0/15 by AMAZON-02 - Amazon.com, Inc. in DE. userdatatrust.com 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 · userdatatrust.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/userdatatrust.com

Resolution chain

IPv6 resolution

No AAAA record for userdatatrust.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
nho@extreme-dm.com, 0ea1003f-4a5c-4cc8-870a-7ea3fd6f2405@identity-protect.org, 16d611b3-974f-4546-8635-44e7b8794b29@identity-protect.org, 343c497c-25eb-4705-a4c5-a8f80b332175@identity-protect.org, 8cc00f3d-5207-4c60-9176-f45b4c74402e@identity-protect.org, c5b495ad-2cec-4ceb-91c6-be44467b3698@identity-protect.org, d0b07de1-cf8b-4fda-9414-31f9a1a0980a@identity-protect.org, owner-2789157@userdatatrust.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-341.awsdns-42.com
  • ns-904.awsdns-49.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-1505.awsdns-60.org
  • ns-1687.awsdns-18.co.uk

MX records

  • userdatatrust-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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