Skip to content

Hostname

mail.myprofilecloud.cfd

Last fetched

mail.myprofilecloud.cfd resolves to 2 IPv4 addresses operated by AS24940 in DE.

Nutrition Label

WHISPER CANON · mail.myprofilecloud.cfdRouting diversity2.4/10Peering density7.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/mail.myprofilecloud.cfd

Resolution chain

mail.myprofilecloud.cfd resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
46.224.86.2846.224.0.0/15AS24940—DE
95.217.34.15795.217.0.0/16AS24940—FI

WHOIS identity

No WHOIS records are currently associated with mail.myprofilecloud.cfd in WhisperGraph.

Threat posture

History

Mail and authentication

MX records

SPF policy

5 SPF mechanisms authorising senders for mail.myprofilecloud.cfd.

MechanismTarget
SPF_Amail.myprofilecloud.cfd
SPF_IP188.34.143.143
SPF_IP46.224.86.28
SPF_IP46.62.141.31
SPF_MXmail.myprofilecloud.cfd

Related pages

Pivot deeper into the graph from mail.myprofilecloud.cfd.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "mail.myprofilecloud.cfd"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

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