Skip to content

Hostname

yesmail.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:299
Registrant organisation
dns admin
Contact emails
dnsadmin@infogroup.com

Subdomains

Subdomain
cdn-ips.yesmail.com
igi.yesmail.com
ns2.yesmail.com
ns3.yesmail.com
ns4.yesmail.com
ns5.yesmail.com
toc.yesmail.com
www.yesmail.com

Showing 8 of 9. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • ns-30.awsdns-03.com
  • ns-886.awsdns-46.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-1531.awsdns-63.org
  • ns-1894.awsdns-44.co.uk

MX records

  • yesmail-com.mail.protection.outlook.com

SPF policy

  • ip: 97.107.16.0/20
  • ip: 206.165.240.0/21
  • ip: 199.125.13.0/24
  • ip: 68.232.140.193/32
  • ip: 216.94.50.3/32
  • ip: 199.125.10.30/31
  • ip: 68.232.137.93/32
  • include: spf.protection.outlook.com
  • a: yesmail.com
  • mx: yesmail.com

Threat-feed evidence

History

Related pages

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