Skip to content

Hostname

luba.nl

Last fetched

luba.nl resolves to 62.165.72.237, announced in 62.165.64.0/18 by PREVIDER-AS - Previder B.V. in NL. luba.nl 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 · luba.nlRouting diversity1.5/10Peering density6.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/luba.nl

Resolution chain

IPv6 resolution

No AAAA record for luba.nl is recorded in WhisperGraph.

Attribution

previder

ORIGIN_AS

WHOIS identity

Registrar
registrar:kpn

Subdomains

Subdomain
ats.luba.nl
autodiscover.luba.nl
carriere.luba.nl
cloud.luba.nl
cockpit.luba.nl
dwl.luba.nl
file.luba.nl
filecap.luba.nl
forh.luba.nl
hf0.luba.nl
hfrh.luba.nl
intercedent.luba.nl

Showing 12 of 27. 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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.kpn.net
  • ns11.kpn.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

  • luba-nl.mail.protection.outlook.com

SPF policy

  • include: _u.luba.nl._spf.dmarclyeu.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: spf.sendinblue.com
  • include: spf.flowmailer.net
  • include: sendgrid.net
  • include: spf.topdesk.net
  • include: spf.afas.online
  • ip: 194.151.7.130
  • ip: 94.107.229.36

Threat-feed evidence

History

Related pages

Pivot from luba.nl 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: "luba.nl"})-[: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.