Hostname
nccwestloop.com
Last fetched
nccwestloop.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in JP. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
nccwestloop.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 18.65.168.128 | 18.65.168.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 18.65.168.14 | 18.65.168.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 18.65.168.40 | 18.65.168.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 18.65.168.93 | 18.65.168.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 18.66.41.10 | 18.66.40.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 18.66.41.106 | 18.66.40.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 18.66.41.124 | 18.66.40.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
| 18.66.41.75 | 18.66.40.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IN |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of nccwestloop.com owner
- Contact emails
- 05713ea8-d5f8-468e-a3d1-8065bd6a6a54@identity-protect.org
- 4adadcb0-ff80-43e4-ab22-7320759f0f55@identity-protect.org
- 64908b71-41bd-4f4d-87b8-54453aa703b4@identity-protect.org
- 7c610851-f19f-4da0-9f2b-458131c85672@identity-protect.org
- 9e52352a-dfb9-4228-8a49-b780dccc58bd@identity-protect.org
- b3a9a0b9-3c91-4983-8bf3-efa84f2dad3b@identity-protect.org
- e7b6320a-0a56-41b2-8e45-4837fbdddbd9@identity-protect.org
Threat posture
History
Related pages
Pivot deeper into the graph from nccwestloop.com.
- IP · 18.65.168.128
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · JP
- Email · 05713ea8-d5f8-468e-a3d1-8065bd6a6a54@identity-protect.org
- TLD · .com
- Browse hostnames · nc…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "nccwestloop.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.