Hostname
yesglasses.com
Last fetched
yesglasses.com resolves to 108.138.106.110, announced in 108.138.106.0/23 by AMAZON-02 - Amazon.com, Inc. in US. yesglasses.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 108.138.106.110
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.123
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.3
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.138.106.86
108.138.106.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 3.170.19.116
- 3.170.19.45
- 3.170.19.73
- 3.170.19.81
- 3.171.61.101
- 3.171.61.53
- 3.171.61.85
- 3.171.61.99
IPv6 resolution
No AAAA record for yesglasses.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:472
- Registrant organisation
- super privacy service c/o dynadot
- Contact emails
- yesglasses.com@superprivacyservice.com, privacy@dynadot.com
Subdomains
Showing 4 of 4 subdomains (4 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
- ns20.digicertdns.com
- ns10.dnsmadeeasy.com
- ns11.dnsmadeeasy.com
- ns12.dnsmadeeasy.com
- ns13.dnsmadeeasy.com
- ns14.dnsmadeeasy.com
- ns15.dnsmadeeasy.com
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
SPF policy
- ip: 52.52.65.200/32
- ip: 52.52.58.30/32
- include: amazonses.com
- include: _spf.google.com
- include: protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from yesglasses.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: "yesglasses.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.