Hostname
ibercoffee.pt
Last fetched
ibercoffee.pt resolves to 104.21.92.39, announced in 104.21.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. ibercoffee.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
- 104.21.92.39
104.21.80.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.4.79
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.5.79
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.40.85
172.66.40.0/21 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.43.171
172.66.40.0/21 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.186.48
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.69.253
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for ibercoffee.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
Showing 4 of 5. View all 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
- aaron.ns.cloudflare.com
- ali.ns.cloudflare.com
MX records
- ibercoffee-pt.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
- include: _spf95.serverhs.org
- a: ibercoffee.pt
- mx: ibercoffee.pt
- ip: 194.39.124.145
- ip: 194.39.124.74
Threat-feed evidence
History
Related pages
Pivot from ibercoffee.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: "ibercoffee.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.