Skip to content

Hostname

intelco.it

Last fetched

intelco.it resolves to 213.158.94.134, announced in 213.158.94.0/23 by COMBELL-AS - Combell NV in BE. intelco.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 · intelco.itRouting diversity2.4/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/intelco.it

Resolution chain

IPv6 resolution

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

Attribution

combell

ORIGIN_AS

WHOIS identity

Registrar
registrar:telecom italia s.p.a.
Registrant organisation
intelco italia informatica

Subdomains

Subdomain
app.intelco.it
ftp.intelco.it
iris-app.intelco.it
iris-app3.intelco.it
iris-test.intelco.it
iris-web.intelco.it
iris.intelco.it
iris2.intelco.it
mail.intelco.it
www.intelco.it

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

  • dns11.interbusiness.it
  • dns5.interbusiness.it
  • dns5-ha.interbusiness.it
  • dns7.interbusiness.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

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

SPF policy

  • include: spf-de.emailsignatures365.com
  • include: musvc.com
  • include: spf.protection.outlook.com
  • include: spf.tmes.trendmicro.com
  • ip: 31.169.106.153
  • ip: 83.221.100.234

Threat-feed evidence

History

Related pages

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