Skip to content

Hostname

named.be

Last fetched

named.be resolves to 94.126.48.73, announced in 94.126.48.0/24 by PI-GROUP - PI-GROUP BV in BE. named.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 · named.beRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint6.0/10canon.whisper.security/host/named.be

Resolution chain

IPv6 resolution

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

Attribution

pi group

ORIGIN_AS

WHOIS identity

Registrar
registrar:webservice

Subdomains

Subdomain
ams.named.be
brussel.named.be
gent1.named.be
gent2.named.be
hole1.named.be
hole2.named.be
kuurne.named.be
mail.named.be
ns1.named.be
ns2.named.be
ns3.named.be
www.named.be

Showing 12 of 12 subdomains (12 per page).

Mail and authentication

Nameservers

  • ns1.named.be
  • ns2.named.be
  • ns3.named.be
  • dns41.cloudns.net
  • dns42.cloudns.net
  • dns43.cloudns.net
  • dns44.cloudns.net

MX records

  • smtp.pi-group.net
  • smtp2.pi-group.net

SPF policy

  • ip: 94.126.48.0/24
  • ip: 2a02:f00::/64
  • ip: 81.171.19.150

Threat-feed evidence

History

Related pages

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