Skip to content

Hostname

nico.it

Last fetched

nico.it resolves to 63.178.140.184, announced in 63.176.0.0/14 by AMAZON-02 - Amazon.com, Inc. in DE. nico.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 · nico.itRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/nico.it

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:seeweb s.r.l.
Registrant organisation
magazzini nico spa

Subdomains

Subdomain
buyerapp.nico.it
capgemini.nico.it
m.nico.it
mail.nico.it
mn.nico.it
staging.nico.it
vpn.nico.it
www.nico.it

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

  • dns.seeweb.it
  • dns2.seeweb.it
  • 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

  • mailsec01.acscloud.eu
  • mailsec02.acscloud.eu

SPF policy

  • ip: 88.63.127.192/28
  • ip: 156.54.15.192/28
  • ip: 212.103.198.240/28
  • include: spf.protection.outlook.com
  • a: mailsec01.acscloud.eu
  • a: mailsec02.acscloud.eu
  • a: esva01.advcloud.it
  • a: esva02.advcloud.it
  • a: esvash.advcloud.it
  • a: mail.advnet-dc.it
  • a: nico.it
  • mx: nico.it
  • a: mail.nico.it

Threat-feed evidence

History

Related pages

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