Hostname
ellation.com
Last fetched
ellation.com resolves to 13.248.160.137, announced in 13.248.160.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. ellation.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
- 13.248.160.137
13.248.160.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 75.2.43.150
75.2.32.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 76.223.34.124
76.223.32.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
- 99.83.186.106
99.83.176.0/20 · AMAZON-02 - Amazon.com, Inc. · Seattle, US
IPv6 resolution
No AAAA record for ellation.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:292
- Registrant organisation
- arlen marmel
- Contact emails
- admin@dnstinations.com, arlen@crunchyroll.com, namecheap@crunchyroll.com, 2db5c68009aa4e42883dd4d7acc4bb2c.protect@whoisguard.com, 29993e0d3f9b45c3b39d1deb95d96707.protect@withheldforprivacy.com, e646e9776a7e4dc6a0053ca6daac9c26.protect@withheldforprivacy.com
Subdomains
| Subdomain |
|---|
| confluence.ellation.com |
| connection.ellation.com |
| intranet.ellation.com |
| jira.ellation.com |
| picksys.ellation.com |
| portal-mail.ellation.com |
| pyxis.ellation.com |
| www.ellation.com |
Showing 8 of 8 subdomains (8 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.
Mail and authentication
Nameservers
- ns-238.awsdns-29.com
- ns-941.awsdns-53.net
- ns-1381.awsdns-44.org
- ns-2007.awsdns-58.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
SPF policy
- include: amazonses.com
- include: _spf.google.com
- include: mg-sfp.greenhouse.io
Threat-feed evidence
History
Related pages
Pivot from ellation.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: "ellation.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.