Skip to content

Hostname

inca.it

Last fetched

inca.it resolves to 149.62.189.95, announced in 149.62.189.0/24 by HOST-SPA - Host SpA in IT. inca.it 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 · inca.itRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/inca.it

Resolution chain

IPv6 resolution

No AAAA record for inca.it is recorded in WhisperGraph.

WHOIS identity

Registrar
registrar:unidata s.p.a.
Registrant organisation
istituto nazionale confederale di assistenza inca

Subdomains

Subdomain
bacheca.inca.it
formazione.inca.it
ftp.inca.it
inca-mta1.inca.it
inca-mta2.inca.it
incamondo.inca.it
ipercorsi.inca.it
manager.inca.it
mx.inca.it
old.inca.it
out.inca.it
pop.inca.it

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

  • 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.uni.net
  • ns2.uni.net

MX records

  • inca-it.mail.protection.outlook.com

SPF policy

  • ip: 188.209.93.192/32
  • ip: 188.209.93.193/32
  • ip: 18.102.174.237/32
  • ip: 156.54.188.52/32
  • ip: 185.241.64.64/27
  • ip: 135.125.205.73/32
  • include: spf.protection.outlook.com
  • a: er.cgil.it
  • a: inca.it
  • mx: inca.it
  • a: posta.cgil.tn.it

Threat-feed evidence

History

Related pages

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