Hostname
bright.ai
Last fetched
bright.ai resolves to 34.216.232.185, announced in 34.208.0.0/12 by AMAZON-02 - Amazon.com, Inc. in US. bright.ai 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
- 34.216.232.185
34.208.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.165.173.176
35.160.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.167.243.193
35.160.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.81.5.57
35.80.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.232.13.216
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.27.108.130
52.24.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.43.194.123
52.40.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.148.201.243
54.148.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.201.244.114
54.200.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 54.69.210.146
54.68.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 16.145.39.11
16.145.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Portland, US
- 16.146.233.101
16.146.128.0/17 · AMAZON-02 - Amazon.com, Inc. · Portland, US
- 16.145.251.101
16.145.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Portland, US
- 184.33.213.190
184.32.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Portland, US
- 184.34.173.16
184.32.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Portland, US
Attribution
Aws
cloud · ORIGIN_AS
Subdomains
| Subdomain |
|---|
| stateful-demo-oilgas.bright.ai |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-304.awsdns-38.com
- ns-938.awsdns-53.net
- ns-1390.awsdns-45.org
- ns-1569.awsdns-04.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Threat-feed evidence
History
Related pages
Pivot from bright.ai 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: "bright.ai"})-[: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.