Skip to content

Hostname

roosit.nl

Last fetched

roosit.nl resolves to 87.233.156.151, announced in 87.233.128.0/18 by TrueServer-AS - TrueFullstaq B.V. in NL. roosit.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 · roosit.nlRouting diversity2.4/10Peering density5.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/roosit.nl

Resolution chain

IPv6 resolution

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

Attribution

truefullstaq

ORIGIN_AS

WHOIS identity

Registrar
registrar:registrar.eu

Subdomains

Subdomain
backup1.roosit.nl
chat.roosit.nl
exchange.roosit.nl
mail.roosit.nl
ns1.roosit.nl
ns2.roosit.nl
roosit03.roosit.nl
rt1.roosit.nl
smtp.roosit.nl
spam1.roosit.nl
spam2.roosit.nl
stats.roosit.nl

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

Mail and authentication

Nameservers

  • 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
  • ns1.roosit.nl
  • ns2.roosit.nl

MX records

  • spam1.roosit.eu
  • spam2.roosit.eu

SPF policy

  • a: app1.roosit.eu
  • a: cron1.roosit.eu
  • a: krakow.roosit.eu
  • a: out.roosit.eu
  • a: webmail.roosit.eu
  • a: www.roosit.eu
  • mx: roosit.nl
  • a: smtp.roosit.nl
  • ip: 212.19.193.158
  • ip: 212.19.193.161
  • ip: 212.19.193.162
  • ip: 212.26.193.42
  • ip: 87.233.156.141

Threat-feed evidence

History

Related pages

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