Skip to content

Hostname

cipal.be

Last fetched

cipal.be resolves to 193.190.121.218, announced in 193.190.0.0/15 by BELNET - BELNET in BE. cipal.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 · cipal.beRouting diversity1.5/10Peering density7.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/cipal.be

Resolution chain

IPv6 resolution

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

Attribution

belnet

ORIGIN_AS

WHOIS identity

Registrar
registrar:cipal it solutions nv

Subdomains

Subdomain
adex.cipal.be
adsmidmz.cipal.be
autodiscover.cipal.be
axsgate.cipal.be
beleid.cipal.be
brocade.cipal.be
cipaleid.cipal.be
cipaltoken.cipal.be
cishare.cipal.be
connect.cipal.be
cover.cipal.be
cs_idmz.cipal.be

Showing 12 of 66. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • gedcex01.adex.cipal.be
  • ns.cipal.be
  • ns2.cipal.be
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • cipal-be.mail.protection.outlook.com

SPF policy

  • ip: 193.190.121.0/24
  • ip: 52.31.106.198/32
  • ip: 52.208.126.243/32
  • ip: 193.190.120.64/27
  • a: cipal.be
  • mx: cipal.be
  • include: spf.protection.outlook.com
  • include: spf.flexmail.eu
  • include: servers.mcsv.net
  • include: spf.topdesk.net

Threat-feed evidence

History

Related pages

Pivot from cipal.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: "cipal.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.