Hostname
fortunamor.com
Last fetched
fortunamor.com resolves to 104.18.12.185, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. fortunamor.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.12.185
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.13.185
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 8.47.69.0
8.47.69.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Bratislava, SK
- 8.6.112.0
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1387
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- baa5cd05e4@fortunamor.com.whoistrustee.com, 228c59f71c9934af41c3f0724d8672d50abeb0e0d9b7f4c730bc7802f708af39@fortunamor.com.whoisproxy.org, 4260004833d1bb765f1a78a32f46909872f46b1af5ebd42aaa108b5a829c8e29@fortunamor.com.whoisproxy.org, 46a2aa1a171a4f6650f08bd80e89eb8dcf034549216d7d859190b509b87c03ee@fortunamor.com.whoisproxy.org, 677e731eeb6a1c7dc5a5577fc951f23ce1687223e61b472c3134f9e671454052@fortunamor.com.whoisproxy.org, 8fe810f3e951cfdd53239b00fafb161ef5df17bf86b170915d082ff572618a90@fortunamor.com.whoisproxy.org, f832c20ec8e126dd694f38d1cf60b5d9e857e1ac0c592363088dff30434545b6@fortunamor.com.whoisproxy.org
Subdomains
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- heather.ns.cloudflare.com
- ned.ns.cloudflare.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
- include: _spf.google.com
- include: mail.zendesk.com
- include: spf.sendios.io
Threat-feed evidence
History
Related pages
Pivot from fortunamor.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: "fortunamor.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.