Hostname
projectkv.com
Last fetched
projectkv.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
projectkv.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 |
|---|---|---|---|---|
| 100.29.199.68 | 100.24.0.0/13 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 100.49.170.210 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 100.52.159.169 | 100.48.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 3.212.67.14 | 3.208.0.0/12 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.0.47.239 | 52.0.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.2.241.241 | 52.2.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.2.243.132 | 52.2.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.20.127.148 | 52.20.0.0/14 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 52.44.75.123 | 52.44.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.196.137.248 | 54.196.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.226.28.2 | 54.226.0.0/15 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
| 54.237.159.119 | 54.237.0.0/16 | AS14618 | AMAZON-AES - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of projectkv.com owner
- Contact emails
- dbabbit@me.com
- 49ab0cae-bb09-4da4-8e6a-88710aa44f1e@identity-protect.org
- 66bd81e1-fdd9-4b25-91ac-61c0c2f8936f@identity-protect.org
- 6df9caa4-9f30-4bcf-9598-9359c10b6430@identity-protect.org
- 8fc708e9-849b-4a5e-ba03-3388e3c5edd9@identity-protect.org
- 90d0dfb3-343c-4d13-934b-4d53dc050adc@identity-protect.org
- eea53a1c-5861-4ff6-80c9-a48e636c1680@identity-protect.org
- fd97aca5-800d-453c-ad19-dcd1ef6630e4@identity-protect.org
Subdomains
3 observed subdomains of projectkv.com.
Threat posture
History
Related pages
Pivot deeper into the graph from projectkv.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "projectkv.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.