Skip to content

Hostname

itool.net

Last fetched

itool.net resolves to 178.20.52.141, announced in 178.20.48.0/21 by IELO - IELO-LIAZO SERVICES SAS in FR. itool.net 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 · itool.netRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/itool.net

Resolution chain

IPv6 resolution

No AAAA record for itool.net is recorded in WhisperGraph.

Attribution

ielo liazo

ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
christophe plessis
Contact emails
4af211e0fe41e87b4826c0597f4a646d-18110843@contact.gandi.net, 9c4d21113412060d966d2efc07c95e8d-650745@contact.gandi.net

Subdomains

Subdomain
applis.itool.net
asp.itool.net
cs.itool.net
fw1.itool.net
fw2.itool.net
smtp.itool.net
static.itool.net
webapps.itool.net
wiki.itool.net

Showing 9 of 9 subdomains (9 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

Mail and authentication

Nameservers

  • ns-139-c.gandi.net
  • ns-154-a.gandi.net
  • ns-223-b.gandi.net
  • ns1.gandi.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

  • smtp.itool.net

SPF policy

  • ip: 81.252.131.0/25
  • ip: 178.20.52.128/26
  • include: spf.mailjet.com
  • mx: itool.net

Threat-feed evidence

History

Related pages

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