Hostname
wishdates.com
Last fetched
wishdates.com resolves to 104.18.22.151, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. wishdates.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.22.151
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.23.151
104.18.16.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
- wishdates.com@domainsbyproxy.com, home.tye@gmail.com, a04ec9f1d7@wishdates.com.whoistrustee.com, 6b8a08a62be085fb872f1ef5ff66351f246d5dad0144e640d3f18a292c694ead@wishdates.com.whoisproxy.org, 8f0f9b17ae5d6427e15401e85d37cc72fea710c36f53a3d01025757419dc507b@wishdates.com.whoisproxy.org, affde34f847766dff7c557e08629b631dcaec4fd8b2680973d4a4fd1185ecb0a@wishdates.com.whoisproxy.org, b0e662ec3a7ddf600f4310277e800ea5a3bb9c1358c45d886498b03cc8128f8e@wishdates.com.whoisproxy.org, e231f2936b4b38c2aa8e3fa9d840d44a075d8b9bd94c2fbd4564623417885ccd@wishdates.com.whoisproxy.org
Subdomains
Showing 4 of 4 subdomains (4 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
- 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 wishdates.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: "wishdates.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.