Skip to content

Hostname

well-fair.nl

Last fetched

well-fair.nl resolves to 199.60.103.105, announced in 199.60.103.0/24 by CLOUDFLARESPECTRUM - Cloudflare London, LLC in US. well-fair.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 · well-fair.nlRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/well-fair.nl

Resolution chain

Attribution

cloudflare london

ORIGIN_AS

WHOIS identity

Registrar
registrar:realtime register

Subdomains

Subdomain
aquapas.well-fair.nl
configurator.well-fair.nl
crm.well-fair.nl
download.well-fair.nl
formhandler.well-fair.nl
klantenpas.well-fair.nl
mail.well-fair.nl
nieuw.well-fair.nl
postcode.well-fair.nl
reisbevestiging.well-fair.nl
sql.well-fair.nl
sync.well-fair.nl

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

  • dns.resolver.domains
  • 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
  • be.ns.vip.nl
  • nl.ns.vip.nl

MX records

  • wellfair-nl01b.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: 20032204.spf07.hubspotemail.net
  • include: sendgrid.net
  • include: spf.eprov.nl
  • a: well-fair.nl
  • ip: 185.27.141.67
  • ip: 31.161.79.107
  • ip: 62.84.247.175
  • ip: 85.214.53.167

Threat-feed evidence

History

Related pages

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