Skip to content

Hostname

mcm.be

Last fetched

mcm.be resolves to 213.181.52.139, announced in 213.181.32.0/19 by PROXIMUS-ISP-AS - Proximus NV in BE. mcm.be 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 · mcm.beRouting diversity1.5/10Peering density4.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/mcm.be

Resolution chain

IPv6 resolution

No AAAA record for mcm.be is recorded in WhisperGraph.

Attribution

proximus

ORIGIN_AS

WHOIS identity

Registrar
registrar:synergics cvba

Subdomains

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • name01.mcm.be
  • name02.mcm.be
  • auth00.ns.be.uu.net
  • auth50.ns.be.uu.net

SPF policy

  • mx: mcm.be
  • a: remailer105.synergics.be
  • a: remailer106.synergics.be
  • a: remailer107.synergics.be
  • a: remailer108.synergics.be
  • a: remailer109.synergics.be
  • a: remailer110.synergics.be
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

Pivot from mcm.be 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: "mcm.be"})-[: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.