Hostname
usiminas.com
Last fetched
usiminas.com resolves to 189.53.5.34, announced in 189.53.0.0/16 by AS4230 - CLARO S.A. in BR. usiminas.com 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
- 189.53.5.34
189.53.0.0/16 · AS4230 - CLARO S.A. · Belo Horizonte, BR
IPv6 resolution
No AAAA record for usiminas.com is recorded in WhisperGraph.
Attribution
claro
ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- perfect privacy,
- Contact emails
- b33q788m8uv@networksolutionsprivateregistration.com, cn8fe5bw54z@networksolutionsprivateregistration.com, hk83k6xj4u6@networksolutionsprivateregistration.com, ht4hv4rh3dg@networksolutionsprivateregistration.com, mh8m24x9899@networksolutionsprivateregistration.com, segurancadainformacao@usiminas.com, sx9rj4rw9w2@networksolutionsprivateregistration.com, ty84n6sb6fu@networksolutionsprivateregistration.com, ut9mw72d3kr@networksolutionsprivateregistration.com, vt5ku5r88zy@networksolutionsprivateregistration.com, xg45b3vy3cu@networksolutionsprivateregistration.com, ym8wz5up6qr@networksolutionsprivateregistration.com, zf88a5us38e@networksolutionsprivateregistration.com
Subdomains
Showing 12 of 90. 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.
Sample inbound links
Mail and authentication
Nameservers
- dns01.usiminas.com.br
- dns02.usiminas.com.br
- dns04.usiminas.com.br
- dns05.usiminas.com.br
MX records
- cluster1.us.messagelabs.com
- cluster1a.us.messagelabs.com
SPF policy
- include: _spf.google.com
- include: spf.messagelabs.com
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from usiminas.com 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: "usiminas.com"})-[: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.