Hostname
opaque.com.br
Last fetched
opaque.com.br resolves to 177.126.186.186, announced in 177.126.160.0/19 by Equinix - Equinix (EMEA) Acquisition Enterprises B.V. in BR. opaque.com.br 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
- 177.126.186.186
177.126.160.0/19 · Equinix - Equinix (EMEA) Acquisition Enterprises B.V. · São Paulo, BR
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 52.8.174.221
52.8.0.0/16 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrant organisation
- ks cosmeticos ltda
- Contact emails
- kim@opaque.com.br
Subdomains
| Subdomain |
|---|
| d-app.opaque.com.br |
| d-click.opaque.com.br |
| d-image.opaque.com.br |
| d-view.opaque.com.br |
| imagens.opaque.com.br |
| mkt.opaque.com.br |
| nitro.opaque.com.br |
| phpmyadmin.opaque.com.br |
| www.opaque.com.br |
Showing 9 of 9 subdomains (9 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
- ns-158.awsdns-19.com
- alaric.ns.cloudflare.com
- maleah.ns.cloudflare.com
- ns-661.awsdns-18.net
- ns-1217.awsdns-24.org
- ns-1991.awsdns-56.co.uk
MX records
- opaque-com-br.mail.protection.outlook.com
SPF policy
- a: opaque.com.br
- mx: opaque.com.br
- include: _spf.criaenvio.com
- include: _spf.elasticemail.com
- include: _spf2.kmitd.com
- include: 8705.meuspf.com
- include: spf.protection.outlook.com
- include: mailgun.org
- ip: 151.80.43.186
Threat-feed evidence
History
Related pages
Pivot from opaque.com.br 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: "opaque.com.br"})-[: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.