Hostname
cellsavers.com
Last fetched
cellsavers.com resolves to 3.217.83.106, announced in 3.208.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. cellsavers.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
- 3.217.83.106
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.233.95.88
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 50.17.213.8
50.17.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.210.87.13
54.210.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for cellsavers.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- cellsavers
- Contact emails
- eyal@cellsavers.com, mohamed@adam.md, 224059ef-4bbc-4d50-a4e5-41d377a17c71@identity-protect.org, 6aa4ec15-3295-45fe-9ad0-e46af79da0b7@identity-protect.org
Subdomains
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
Sample outbound links
Mail and authentication
Nameservers
- ns-455.awsdns-56.com
- ns-991.awsdns-59.net
- ns-1532.awsdns-63.org
- ns-1885.awsdns-43.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 cellsavers.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: "cellsavers.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.