Skip to content

Hostname

dns.watch

Last fetched

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

Resolution chain

IPv6 resolution

No AAAA record for dns.watch is recorded in WhisperGraph.

Attribution

Aws

cloud · DNS_OPERATOR, ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
whois-to@iamonsys.com

Subdomains

Subdomain
resolver1.dns.watch
resolver2.dns.watch

Showing 2 of 2 subdomains (2 per page).

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

Mail and authentication

Nameservers

  • ns-86.awsdns-10.com
  • ns-807.awsdns-36.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-1326.awsdns-37.org
  • ns-1664.awsdns-16.co.uk

Threat-feed evidence

History

Related pages

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