Skip to content

Hostname

vipit.be

Last fetched

vipit.be resolves to 188.40.241.197, announced in 188.40.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. vipit.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 · vipit.beRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.5/10canon.whisper.security/host/vipit.be

Resolution chain

IPv6 resolution

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

Attribution

hetzner

ORIGIN_AS

WHOIS identity

Registrar
registrar:willux.be nv

Subdomains

Subdomain
barracuda.vipit.be
cloud.vipit.be
dc2.vipit.be
dnsadmin.vipit.be
hosting.vipit.be
mail.vipit.be
mailhost2.vipit.be
noc.vipit.be
ns1.vipit.be
ns2.vipit.be
ns3.vipit.be
ns4.vipit.be

Showing 12 of 30. View all subdomains →

Mail and authentication

Nameservers

  • noc.vipit.be
  • ns1.vipit.be
  • ns2.vipit.be
  • ns3.vipit.be
  • ns5.vipit.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

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

SPF policy

  • ip: 44.31.68.0/24
  • ip: 194.50.91.0/27
  • ip: 2a01:4f8:100:2383::/64
  • ip: 2a02:1807:2720:100::/56
  • a: telenet.be
  • include: _spf.telenet-ops.be
  • mx: vipit.be
  • include: spf.protection.outlook.com
  • ip: 188.40.241.193
  • ip: 188.40.241.197
  • ip: 193.30.110.65
  • ip: 62.210.170.130
  • ip: 78.46.93.181
  • ip: 81.82.252.148

Threat-feed evidence

History

Related pages

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