Skip to content

Hostname

leone.si

Last fetched

leone.si resolves to 46.19.10.38, announced in 46.19.10.0/23 by SIEL - SIEL, d.o.o. in SI. leone.si 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 · leone.siRouting diversity1.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/leone.si

Resolution chain

IPv6 resolution

No AAAA record for leone.si is recorded in WhisperGraph.

Attribution

siel

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for leone.si. 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

Subdomain
allforteam.leone.si
autodiscover.leone.si
dostop.leone.si
host.leone.si
mail.leone.si
mailsrv.leone.si
malica.leone.si
remote.leone.si
vpn.leone.si
www.leone.si

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

Sample outbound links

Mail and authentication

Nameservers

  • ns3.dikadom.com
  • 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
  • ns01.b-s.si
  • ns02.b-s.si

MX records

  • mail.leone.si
  • leone-si.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • a: mail.leone.si
  • ip: 193.77.69.54
  • ip: 193.95.247.77

Threat-feed evidence

History

Related pages

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