Hostname
directvgo.com.br
Last fetched
directvgo.com.br resolves to 100.24.186.23, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. directvgo.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
- 100.24.186.23
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.30.165.96
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.218.100.143
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.220.78.34
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.230.167.104
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.200.101.251
52.200.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for directvgo.com.br is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrant organisation
- jose viera zarate
- Contact emails
- brazil@latintld.com
Subdomains
| Subdomain |
|---|
| www.directvgo.com.br |
Showing 1 of 1 subdomain (1 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
Sample outbound links
Mail and authentication
Nameservers
- ns-122.awsdns-15.com
- ns-889.awsdns-47.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1531.awsdns-63.org
- ns-1989.awsdns-56.co.uk
MX records
- inbound-smtp.us-east-1.amazonaws.com
SPF policy
- include: _spf.directtalk.com.br
- include: amazonses.com
Threat-feed evidence
History
Related pages
Pivot from directvgo.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: "directvgo.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.