Hostname
bitsige.com
Last fetched
bitsige.com resolves to 12 IPv4 addresses operated by AMAZON-AES - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
bitsige.com resolves to 12 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.215.245.89 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.220.78.160 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.221.162.203 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.230.117.152 | 3.224.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 34.206.192.235 | 34.192.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 35.174.215.71 | 35.168.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 44.199.130.68 | 44.192.0.0/11 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.0.6.172 | 52.0.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.54.120.215 | 52.54.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 72.44.43.225 | 72.44.40.0/21 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.86.198.89 | 98.80.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 98.95.64.243 | 98.88.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of bitsige.com owner
- Contact emails
Subdomains
1 observed subdomain of bitsige.com.
| Subdomain |
|---|
| wildcard.bitsige.com |
Threat posture
History
Related pages
Pivot deeper into the graph from bitsige.com.
- IP · 3.215.245.89
- ASN · AS14618AMAZON-AES - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · 281ccb5f-8213-4aee-a8aa-8adb15d2cb9e@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: "bitsige.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.