Skip to content

Hostname

toolineo.de

Last fetched

toolineo.de resolves to 4.210.164.172, announced in 4.208.0.0/12 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in NL. toolineo.de 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 · toolineo.deRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/toolineo.de

Resolution chain

IPv6 resolution

No AAAA record for toolineo.de is recorded in WhisperGraph.

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for toolineo.de. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns.inwx.de
  • ns2.inwx.de
  • ns3.inwx.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

MX records

  • toolineo-de.mail.protection.outlook.com

SPF policy

  • ip: 62.50.125.28/32
  • include: spf.protection.outlook.com
  • include: asta-arbeitsschutz.de
  • include: spf.srv2.de
  • ip: 185.244.194.184
  • ip: 212.211.154.28
  • ip: 212.211.155.28
  • ip: 212.211.214.245
  • ip: 212.211.217.240
  • ip: 62.50.125.30
  • ip: 91.24.53.169

Threat-feed evidence

History

Related pages

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