Skip to content

Hostname

crb-batiment.com

Last fetched

crb-batiment.com resolves to 90.16.100.209, announced in 90.16.0.0/17 by AS3215 - Orange S.A. in FR. crb-batiment.com 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 · crb-batiment.comRouting diversity1.5/10Peering density8.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/crb-batiment.com

Resolution chain

IPv6 resolution

No AAAA record for crb-batiment.com is recorded in WhisperGraph.

Attribution

orange

ORIGIN_AS

WHOIS identity

Registrar
iana:433
Registrant organisation
crb
Contact emails
0xjzguqqpdt6t595ja5j@o.o-w-o.info, dv1zapshjc1qfmrx34ck@k.o-w-o.info, iu07y7zc3gu6jl8o94ay@n.o-w-o.info, kqmceyemg1u47o0pvu4x@l.o-w-o.info

Subdomains

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • dns17.ovh.net
  • ns17.ovh.net
  • 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

  • vade-mx-eu-fallback01.hornetsecurity.com
  • vade-mx-eu-fallback02.hornetsecurity.com
  • vade-mx-fr01.hornetsecurity.com
  • vade-mx-fr02.hornetsecurity.com

SPF policy

  • a: crb-batiment.com
  • mx: crb-batiment.com
  • include: spf.hornetsecurity.com
  • ip: 109.190.155.170
  • ip: 90.16.100.209

Threat-feed evidence

History

Related pages

Pivot from crb-batiment.com 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: "crb-batiment.com"})-[: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.