Skip to content

Hostname

cm.be

Last fetched

cm.be resolves to 12 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists registrar:name: getronics belgium sa/nv|website: www.getronics.com|| as the registrar.

Nutrition Label

WHISPER CANON · cm.beRouting diversity3.0/10Peering density9.2/10MOAS conflict✓ noneThreat-feed listings6.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/cm.be

Resolution chain

cm.be resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
13.33.67.3413.33.64.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
13.33.67.6013.33.64.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
13.33.67.6113.33.64.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
13.33.67.9313.33.64.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
3.162.112.383.162.112.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
3.162.112.623.162.112.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
3.162.112.663.162.112.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
3.162.112.763.162.112.0/21AS16509AMAZON-02 - Amazon.com, Inc.US
52.222.236.2852.222.236.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
52.222.236.3152.222.236.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
52.222.236.6652.222.236.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE
52.222.236.9352.222.236.0/23AS16509AMAZON-02 - Amazon.com, Inc.DE

WHOIS identity

Registrar
registrar:name: getronics belgium sa/nv|website: www.getronics.com||
Organization
Contact emails

Subdomains

81 observed subdomains of cm.be.

Web-graph footprint

Distinct hostnames that link to or from cm.be in the public web crawl.

1,495 sites link to this hostname.

Threat posture

History

Mail and authentication

SPF policy

5 SPF mechanisms authorising senders for cm.be.

MechanismTarget
SPF_INCLUDEmmail.mc.be
SPF_INCLUDEseagma-mailout-web.maehdros.be
SPF_INCLUDEspf.formdesk.com
SPF_INCLUDEspf.protection.outlook.com
SPF_INCLUDEspf2.cm.be

Related pages

Pivot deeper into the graph from cm.be.

Cypher and MCP

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

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