Hostname
opzoom.com
Last fetched
opzoom.com resolves to 108.139.47.129, announced in 108.139.44.0/22 by AMAZON-02 - Amazon.com, Inc. in US. opzoom.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
- 108.139.47.129
108.139.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.139.47.29
108.139.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.139.47.51
108.139.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.139.47.66
108.139.44.0/22 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 54.192.151.102
54.192.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.104
54.192.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.117
54.192.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
- 54.192.151.98
54.192.148.0/22 · AMAZON-02 - Amazon.com, Inc. · Kolkata, IN
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- domain privacy
- Contact emails
- 1720719731@qq.com, b37fca14fccb420bbf0eccf6a1c1c612.protect@whoisguard.com, 1d22c9c618d7423596f81f4d26545c86.protect@withheldforprivacy.com, opzoomcom@obscure.me
Subdomains
| Subdomain |
|---|
| app.opzoom.com |
| chat.opzoom.com |
| cicd.opzoom.com |
| docs.opzoom.com |
| file.opzoom.com |
| listings-daisy.opzoom.com |
| mail.opzoom.com |
| test-tpg.opzoom.com |
| www-itombs.opzoom.com |
| www.opzoom.com |
Showing 10 of 10 subdomains (10 per page).
Mail and authentication
Nameservers
- ns-87.awsdns-10.com
- ns-641.awsdns-16.net
- ns-1079.awsdns-06.org
- ns-1760.awsdns-28.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
SPF policy
- include: amazonses.com
- include: _spf.google.com
Threat-feed evidence
History
Related pages
Pivot from opzoom.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: "opzoom.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.