Hostname
pkpd.net
Last fetched
pkpd.net resolves to 3.175.64.103, announced in 3.175.64.0/21 by AMAZON-02 - Amazon.com, Inc. in CA. pkpd.net 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
- 3.175.64.103
3.175.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Vancouver, CA
- 3.175.64.18
3.175.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Vancouver, CA
- 3.175.64.45
3.175.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Vancouver, CA
- 3.175.64.88
3.175.64.0/21 · AMAZON-02 - Amazon.com, Inc. · Vancouver, CA
- 99.84.91.117
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.127
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.45
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
- 99.84.91.81
99.84.88.0/21 · AMAZON-02 - Amazon.com, Inc. · Vienna, AT
IPv6 resolution
No AAAA record for pkpd.net is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- bloom, lois
- Contact emails
- 79585027@qq.com, bassta@yandex.com, lbloom@aaacis.net, 29df1b91-fd8d-4205-9c81-a431e3dda2f7@identity-protect.org, 44224bd8-d53c-465e-ae1e-0ae1577c128f@identity-protect.org, 4e0ce3fb-1b97-4f1e-b04b-d787f21c2af3@identity-protect.org, 5d47c5ac-4c9b-47ed-8a40-f48ef452b6e9@identity-protect.org, 88163529-7c9f-4d2b-8d72-e99d17c582f6@identity-protect.org, eb698787-1402-4283-b24a-c5d0a8f692f0@identity-protect.org
Subdomains
| Subdomain |
|---|
| epic.pkpd.net |
| www.pkpd.net |
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-501.awsdns-62.com
- ns-656.awsdns-18.net
- ns-1361.awsdns-42.org
- ns-1965.awsdns-53.co.uk
Threat-feed evidence
History
Related pages
Pivot from pkpd.net 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: "pkpd.net"})-[: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.