Skip to content

Hostname

remote.checkmatefire.com

Last fetched

remote.checkmatefire.com resolves to 1 IPv4 address operated by AKAMAI-LINODE-AP Akamai Connected Cloud in GB.

Nutrition Label

WHISPER CANON · remote.checkmatefire.comRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/remote.checkmatefire.com

Resolution chain

remote.checkmatefire.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
139.162.192.235139.162.192.0/19AS63949AKAMAI-LINODE-AP Akamai Connected CloudGB

WHOIS identity

No WHOIS records are currently associated with remote.checkmatefire.com in WhisperGraph.

Threat posture

History

Mail and authentication

MX records

SPF policy

5 SPF mechanisms authorising senders for remote.checkmatefire.com.

MechanismTarget
SPF_INCLUDEaspmx.pardot.com
SPF_INCLUDEspf.exclaimer.net
SPF_INCLUDEspf.protection.outlook.com
SPF_INCLUDEspf.ukservers.net
SPF_IP192.254.125.237/32

Related pages

Pivot deeper into the graph from remote.checkmatefire.com.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "remote.checkmatefire.com"})-[: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.