Hostname
sedna360.com
Last fetched
sedna360.com resolves to 104.21.37.122, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. sedna360.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.21.37.122
104.21.32.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.208.26
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1534
- Registrant organisation
- domain admin, c/o id#10760
- Contact emails
- gdpr-masking@gdpr-masked.com, contact@privacyprotect.org, oguzhan@kod.com.tr
Subdomains
| Subdomain |
|---|
| akka.sedna360.com |
| antedon.sedna360.com |
| b2b.sedna360.com |
| hrsaws.sedna360.com |
| kod.sedna360.com |
| reservation.sedna360.com |
| test.sedna360.com |
| turunchotels.sedna360.com |
| www.sedna360.com |
Showing 9 of 9 subdomains (9 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
- arnold.ns.cloudflare.com
- aurora.ns.cloudflare.com
- 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
MX records
- sedna360-com.mail.protection.outlook.com
SPF policy
- include: spf.mandrillapp.com
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from sedna360.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: "sedna360.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.