Skip to content

Hostname

fidus.nl

Last fetched

fidus.nl resolves to 85.10.139.67, announced in 85.10.128.0/19 by TRANSIP-AS - Signet B.V. in FR. fidus.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 · fidus.nlRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/fidus.nl

Resolution chain

IPv6 resolution

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

Attribution

signet

ORIGIN_AS

WHOIS identity

Registrar
registrar:team.blue nl b.v.

Subdomains

Subdomain
berichten.fidus.nl
campaigns.fidus.nl
cms.fidus.nl
hypotheken.fidus.nl
mijn.fidus.nl
testberichten.fidus.nl
waarderapport.fidus.nl
www.fidus.nl

Showing 8 of 8 subdomains (8 per page).

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.vercel-dns.com
  • ns2.transip.eu
  • 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
  • ns0.transip.net
  • ns1.transip.nl

MX records

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

SPF policy

  • include: amazonses.com
  • include: spf-de.emailsignatures365.com
  • include: spf.mailjet.com
  • include: spf.protection.outlook.com
  • include: _spf.awisoftware.nl
  • include: spf.hdconnect.nl
  • include: _spf.realworks.nl
  • include: spf.afas.online
  • include: _spf.eu.mailgun.org

Threat-feed evidence

History

Related pages

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