Skip to content

Hostname

ionlake.com

Last fetched

ionlake.com resolves to 104.17.47.19, announced in 104.17.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ionlake.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · ionlake.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/ionlake.com

Resolution chain

IPv6 resolution

No AAAA record for ionlake.com is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of ionlake.com owner
Contact emails
2405d125-2c34-40da-add3-bf3f9b4fa447@identity-protect.org, 58e2fe3e-9134-4bb0-bf6f-946bf56b646d@identity-protect.org, 83769d05-8522-4b58-8101-e9e12e925786@identity-protect.org, a10ad1e1-2f34-4561-b7dd-777b6f55239a@identity-protect.org, a70869d2-d068-4872-a924-ec99f038180f@identity-protect.org, b6c5aa27-2267-431d-86ff-90f3eb1f1e47@identity-protect.org, owner-10862809@ionlake.com.whoisprivacyservice.org, owner-1293954@ionlake.com.whoisprivacyservice.org, owner-5381093@ionlake.com.whoisprivacyservice.org, owner@ionlake.com.whoisprivacyservice.org

Subdomains

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-169.awsdns-21.com
  • ns-909.awsdns-49.net
  • ns-1277.awsdns-31.org
  • ns-1768.awsdns-29.co.uk

MX records

  • ionlake-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: vtigermails.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

Pivot from ionlake.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: "ionlake.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.