Hostname
seen.com
Last fetched
seen.com resolves to 104.18.26.45, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. seen.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
- 104.18.26.45
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.27.45
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 18.211.166.153
18.208.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.202.203.47
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.243.86.28
54.242.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1910
- Registrant organisation
- chad wright
- Contact emails
- seen.com@domainsbyproxy.com, hdqhlmcpyl@whoisprivacyprotect.com, hhnxfrrhvp@whoisprivacyprotect.com, kddqrlvp@whoisprivacyprotect.com, ksbbwrfn@whoisprivacyprotect.com, lgywkvhtnq@whoisprivacyprotect.com, mmhjtqkr@whoisprivacyprotect.com, pwkcxydhwq@whoisprivacyprotect.com, qnsbmsytv@whoisprivacyprotect.com, qxsqpbkdbf@whoisprivacyprotect.com, tkdtbvtfx@whoisprivacyprotect.com, tknlrjhptq@whoisprivacyprotect.com, tlbhjwcc@whoisprivacyprotect.com, tplhvpgm@whoisprivacyprotect.com, vgxkjlxm@whoisprivacyprotect.com, webquest@gmail.com, xsfrlbws@whoisprivacyprotect.com, yygmfbqt@whoisprivacyprotect.com
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
Mail and authentication
Nameservers
- arturo.ns.cloudflare.com
- jacqueline.ns.cloudflare.com
MX records
- seen-com.mail.protection.outlook.com
SPF policy
- include: _spf.i2cinc.com
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from seen.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: "seen.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.