Skip to content

Hostname

sayyes.com

Last fetched

sayyes.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. sayyes.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 · sayyes.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/sayyes.com

Resolution chain

No IPv4 resolution is recorded for sayyes.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of sayyes.com owner
Contact emails
af2fb3zm29r@networksolutionsprivateregistration.com, bw5pq5ts5cw@networksolutionsprivateregistration.com, g34yx99x7qw@networksolutionsprivateregistration.com, hj25598g8ra@networksolutionsprivateregistration.com, hj7u64kh9gc@networksolutionsprivateregistration.com, qr8fh8d346q@networksolutionsprivateregistration.com, jared.stanley@gmail.com, xm63785j6a4@networksolutionsprivateregistration.com, y75fr8sk8fa@networksolutionsprivateregistration.com, 34c11814-f32e-48ff-91f2-98b127a7ea4f@identity-protect.org, 49255df7-48ec-483a-aab5-0f57dd7c4b16@identity-protect.org, 9cecfce4-c373-4996-83ea-251eac57e92e@identity-protect.org, afbcdfeb-ff85-482e-aec8-f7a0de4495f5@identity-protect.org, b3c77780-0f5d-4732-be5d-a340036b4c49@identity-protect.org, f0312544-67e5-4720-b14d-90057c6124af@identity-protect.org, owner-10458168@sayyes.com.whoisprivacyservice.org, owner-11315784@sayyes.com.whoisprivacyservice.org, owner-3831067@sayyes.com.whoisprivacyservice.org, owner-5031199@sayyes.com.whoisprivacyservice.org, owner-5228581@sayyes.com.whoisprivacyservice.org and 3 more

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-24.awsdns-03.com
  • ns-531.awsdns-02.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-1447.awsdns-52.org
  • ns-1925.awsdns-48.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Threat-feed evidence

History

Related pages

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