Skip to content

Hostname

managed.peakpulse.email

Last fetched

managed.peakpulse.email resolves to 5 IPv4 addresses operated by AS16276 in FR.

Nutrition Label

WHISPER CANON · managed.peakpulse.emailRouting diversity3.9/10Peering density9.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint7.6/10canon.whisper.security/host/managed.peakpulse.email

Resolution chain

managed.peakpulse.email resolves to 5 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
164.132.95.126164.132.0.0/16AS16276—FR
188.165.1.80188.165.0.0/16AS16276—FR
46.105.88.23446.105.0.0/16AS16276—FR
54.38.226.14054.38.0.0/16AS16276—FR
94.23.161.1994.23.0.0/16AS16276—FR

WHOIS identity

No WHOIS records are currently associated with managed.peakpulse.email in WhisperGraph.

Threat posture

History

Mail and authentication

SPF policy

3 SPF mechanisms authorising senders for managed.peakpulse.email.

MechanismTarget
SPF_Amanaged.peakpulse.email
SPF_INCLUDE_spf.elasticemail.com
SPF_MXmanaged.peakpulse.email

Related pages

Pivot deeper into the graph from managed.peakpulse.email.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "managed.peakpulse.email"})-[: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.