Hostname
siag.it
Last fetched
siag.it resolves to 13.107.213.59, announced in 13.104.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in CA. siag.it is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.107.213.59
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.226.45
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Toronto, CA
- 13.107.246.59
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.253.45
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Toronto, CA
- 62.101.0.179
62.101.0.0/24 · SIAG - Informatica Alto Adige Spa · Bolzano, IT
- 150.171.109.100
150.171.0.0/16 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Nairobi, KE
- 150.171.109.101
150.171.0.0/16 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Nairobi, KE
IPv6 resolution
No AAAA record for siag.it is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:informatica alto adige s.p.a.
- Registrant organisation
- suedtiroler informatik ag / informatica alto adige s.p.a.
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns1-09.azure-dns.com
- ns4-09.azure-dns.info
- ns2-09.azure-dns.net
- ns3-09.azure-dns.org
MX records
- mx07-0067de01.pphosted.com
- mx08-0067de01.pphosted.com
SPF policy
- ip: 62.101.0.0/21
- ip: 62.101.8.0/21
- ip: 62.101.1.0/24
- ip: 54.229.2.165/32
- ip: 52.30.130.201/32
- include: musvc.com
- include: spf.protection.outlook.com
- include: spf.sendinblue.com
- include: spf.byway.it
- include: servers.mcsv.net
Threat-feed evidence
History
Related pages
Pivot from siag.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: "siag.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.