Hostname
brihet.com.ar
Last fetched
brihet.com.ar resolves to 104.21.17.149, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. brihet.com.ar 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.17.149
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.177.9
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.1
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.1
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · 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 brihet.com.ar. 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 |
|---|
| correo.brihet.com.ar |
| dev.brihet.com.ar |
| garantizadas.brihet.com.ar |
| salvat.brihet.com.ar |
| www.brihet.com.ar |
Showing 5 of 5 subdomains (5 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
- quinton.ns.cloudflare.com
- sharon.ns.cloudflare.com
MX records
- mx.fibercorp.com.ar
SPF policy
- ip: 24.232.0.0/24
- ip: 201.212.2.128/27
- ip: 181.30.31.32/27
- ip: 181.30.31.8/29
- mx: brihet.com.ar
- include: _spf.google.com
- ip: 149.50.137.141
- ip: 149.50.144.15
- ip: 2800:6c0:5:0:0:0:0:14d2
- ip: 2800:6c0:5:0:0:0:0:dfc
Threat-feed evidence
History
Related pages
Pivot from brihet.com.ar 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: "brihet.com.ar"})-[: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.