Hostname
bigoca.com
Last fetched
bigoca.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
bigoca.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 |
|---|---|---|---|---|
| 3.168.40.112 | 3.168.40.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.40.127 | 3.168.40.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.40.16 | 3.168.40.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.168.40.71 | 3.168.40.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 3.174.113.103 | 3.174.112.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.174.113.41 | 3.174.112.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.174.113.62 | 3.174.112.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
| 3.174.113.73 | 3.174.112.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | FI |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of bigoca.com owner
- Contact emails
- 27b9fdce-4dc3-4c96-869a-e5822c938bfb@identity-protect.org
- 51f4df61-d747-4ac2-9b4b-84dc01dbb30f@identity-protect.org
- 88b56578-470e-4212-b05d-e1e393d6cf4c@identity-protect.org
- b16baaa4-a808-4e49-b416-7a9f333d54a3@identity-protect.org
- c00eef3b-ea16-4e7a-bab5-234cbad432cc@identity-protect.org
- d36907cf-75d1-4dfd-bdc8-788eceb2d1c2@identity-protect.org
- e64717df-76c0-4a8a-bfc9-64da61883d9a@identity-protect.org
Threat posture
History
Related pages
Pivot deeper into the graph from bigoca.com.
- IP · 3.168.40.112
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · 27b9fdce-4dc3-4c96-869a-e5822c938bfb@identity-protect.org
- TLD · .com
- Browse hostnames · bi…
- 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: "bigoca.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.