Hostname
druni.pt
Last fetched
druni.pt resolves to 199.232.193.91, announced in 199.232.192.0/22 by FASTLY - Fastly, Inc. in CA. druni.pt 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
- 199.232.193.91
199.232.192.0/22 · FASTLY - Fastly, Inc. · Montreal, CA
- 199.232.197.91
199.232.196.0/22 · FASTLY - Fastly, Inc. · Montreal, CA
IPv6 resolution
No AAAA record for druni.pt is recorded in WhisperGraph.
Attribution
Fastly
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for druni.pt. 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 |
|---|
| publi.druni.pt |
| publi1.druni.pt |
| publi2.druni.pt |
| publi3.druni.pt |
| publi4.druni.pt |
| publi5.druni.pt |
| publi7.druni.pt |
| www.druni.pt |
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.
Mail and authentication
Nameservers
- ns-44.awsdns-05.com
- ns-578.awsdns-08.net
- 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
- ns-1254.awsdns-28.org
- ns-1799.awsdns-32.co.uk
MX records
- druni-pt.mail.protection.outlook.com
- publi.druni.pt
- publi1.druni.pt
- publi2.druni.pt
- publi3.druni.pt
- publi4.druni.pt
- publi5.druni.pt
- publi7.druni.pt
SPF policy
- ip: 95.60.240.64/28
- include: spf.protection.outlook.com
- mx: druni.pt
Threat-feed evidence
History
Related pages
Pivot from druni.pt 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: "druni.pt"})-[: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.