Hostname
sirenuse.it
Last fetched
sirenuse.it resolves to 104.26.14.148, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. sirenuse.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
- 104.26.14.148
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.15.148
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.73.174
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- registrar:1 api gmbh
- Registrant organisation
- le sirenuse s.p.a.
Subdomains
| Subdomain |
|---|
| mail.sirenuse.it |
| mail1.sirenuse.it |
| mail2.sirenuse.it |
| mail3.sirenuse.it |
| mbox.sirenuse.it |
| whistleblowing.sirenuse.it |
| www.sirenuse.it |
Showing 7 of 7 subdomains (7 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
- julio.ns.cloudflare.com
- nicole.ns.cloudflare.com
- ns1.eurodns.com
- ns2.eurodns.com
- ns3.eurodns.com
- ns4.eurodns.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
MX records
- mail.sirenuse.it
- mail1.sirenuse.it
- mail2.sirenuse.it
- mail3.sirenuse.it
- sirenuse-it.mail.protection.outlook.com
- sirenuse-it.mail.protection.outlook.com.sirenuse.it
SPF policy
- ip: 151.193.18.41/32
- include: spf.iway.ch
- include: _spf.createsend.com
- include: ltxmail.synxis.com
- include: spf.synxis.com
- mx: sirenuse.it
Threat-feed evidence
History
Related pages
Pivot from sirenuse.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: "sirenuse.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.