Skip to content

Hostname

watchdox.com

Last fetched

watchdox.com resolves to 100.29.161.212, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. watchdox.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 · watchdox.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/watchdox.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:292
Registrant organisation
blackberry
Contact emails
5c37e3be0a28fd0a1797bd1257c7e769@domaindiscreet.com, 797e93110a28fd0a23764d2d0d109fe0@domaindiscreet.com, 7cd2fdf60a28fd0a5b17d93ccd6c22a9@domaindiscreet.com, admin@watchdox.com, ba8276ae0a28fd0a05a05d97d4645a91@domaindiscreet.com, c1976d760a28fd0a38d6bbb80ace6b60@domaindiscreet.com, c53d81040a28fd0a06b21f2ef892a9c9@domaindiscreet.com, d35bd80a0a28fd0a6f6bb78ccd5a34f2@domaindiscreet.com, f8p0bi51psjv78sgaulkv3nfge@domaindiscreet.com, dnsadmin@rim.net

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-364.awsdns-45.com
  • ns-898.awsdns-48.net
  • ns-1375.awsdns-43.org
  • ns-1574.awsdns-04.co.uk

MX records

  • mx11.blackberry.com
  • mx12.blackberry.com
  • mx13.blackberry.com
  • mx14.blackberry.com
  • mx15.blackberry.com
  • mx16.blackberry.com
  • mxa-00224f01.gslb.pphosted.com
  • mxb-00224f01.gslb.pphosted.com

SPF policy

  • include: authsmtp.com
  • include: blackberry.com
  • include: _spf.google.com
  • include: aspmx.googlemail.com
  • include: sparkpostmail.com

Threat-feed evidence

History

Related pages

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