Skip to content

Hostname

valid.be

Last fetched

valid.be resolves to 80.85.86.6, announced in 80.85.84.0/22 by AKAMAI-LINODE-AP - Akamai Connected Cloud in GB. valid.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 · valid.beRouting diversity1.5/10Peering density6.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/valid.be

Resolution chain

IPv6 resolution

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

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
registrar:banan bvba

Subdomains

Subdomain
colo.valid.be
home.valid.be
ns-do-ams2.valid.be
ns-do-ams3.valid.be
nsc01.valid.be
nsc02.valid.be
smtp.valid.be
test.valid.be
web-li-lon.valid.be
web6.valid.be
www.valid.be

Showing 11 of 11 subdomains (11 per page).

Mail and authentication

Nameservers

  • ns-do-ams2.valid.be
  • ns-do-ams3.valid.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • a: valid.be
  • mx: valid.be
  • include: _spf.google.com
  • ip: 78.47.242.90
  • ip: 78.47.89.166
  • ip: 88.198.37.24
  • ip: 88.198.65.131

Threat-feed evidence

History

Related pages

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