Hostname
banrishopping.com.br
Last fetched
banrishopping.com.br resolves to 179.191.175.57, announced in 179.191.175.0/24 by AS52580 - Azion Technologies Ltda. in BR. banrishopping.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
- 179.191.175.57
- 179.191.175.65
- 179.191.175.73
- 179.191.177.33
179.191.177.0/24 · AS52580 - Azion Technologies Ltda. · Ashburn, US
- 179.191.182.65
- 179.191.185.64
- 179.191.186.64
- 206.41.72.3
206.41.72.0/24 · BSO - IX Reach Ltd · Seattle, US
- 206.41.72.67
206.41.72.0/24 · BSO - IX Reach Ltd · Seattle, US
- 206.41.74.19
206.41.72.0/21 · BSO - IX Reach Ltd · Atlanta, US
- 206.41.74.3
206.41.72.0/21 · BSO - IX Reach Ltd · Atlanta, US
- 89.30.68.3
IPv6 resolution
Attribution
azion ltda
ORIGIN_AS
WHOIS identity
- Registrant organisation
- banrisul - banco do estado do rio grande do sul
- Contact emails
- dominios@banrisul.com.br
Subdomains
| Subdomain |
|---|
| banspf.banrishopping.com.br |
| mail1.banrishopping.com.br |
| preprod.banrishopping.com.br |
| release.banrishopping.com.br |
| token.banrishopping.com.br |
| www.banrishopping.com.br |
| wwwteste.banrishopping.com.br |
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.
Mail and authentication
Nameservers
- ns2.aziondns.com
- ns1.aziondns.net
- ns3.aziondns.org
MX records
- mail1.banrishopping.com.br
SPF policy
- include: banspf.banrishopping.com.br
- include: spfa.csu.com.br
- include: _spf.google.com
- include: spf.protection.outlook.com
- ip: 131.161.215.115
- ip: 189.44.96.249
- ip: 189.44.96.250
- ip: 189.44.96.252
- ip: 201.45.162.212
- ip: 201.45.162.217
- ip: 201.45.162.218
- ip: 201.45.162.220
Threat-feed evidence
History
Related pages
Pivot from banrishopping.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: "banrishopping.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.