Hostname
hinky.net
Last fetched
hinky.net resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in MY. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
hinky.net 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.67.181.105 | 18.67.196.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MY |
| 18.67.181.61 | 18.67.196.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MY |
| 18.67.181.66 | 18.67.196.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MY |
| 18.67.181.7 | 18.67.196.0/22 | AS16509 | AMAZON-02 - Amazon.com, Inc. | MY |
| 18.67.51.53 | 18.67.59.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 18.67.51.65 | 18.67.59.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 18.67.51.75 | 18.67.59.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 18.67.51.91 | 18.67.59.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
WHOIS identity
- Registrar
- iana:468
- Organization
- identity protection service
- Contact emails
- yuming@yinsibaohu.aliyun.com
- 0fedede8-fcde-4cae-b375-6d5b51c3f433@identity-protect.org
- 10c44c3e-15e5-4da7-9a51-09ce72b8fbbb@identity-protect.org
- 18497948-2506-41fa-b70b-750f3c78c3e1@identity-protect.org
- 1bef930b-99dd-4abc-81a5-a13801527d74@identity-protect.org
- 46684a35-319f-4b1c-ad50-4f9537b52458@identity-protect.org
- c7497f18-aca6-4313-8501-227d6c0b816d@identity-protect.org
- d3c46867-2d5d-46ff-a276-2eafe3f23f77@identity-protect.org
Subdomains
2 observed subdomains of hinky.net.
| Subdomain |
|---|
| api.hinky.net |
| www.hinky.net |
Threat posture
History
Mail and authentication
MX records
Related pages
Pivot deeper into the graph from hinky.net.
- IP · 18.67.181.105
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · MY
- Email · yuming@yinsibaohu.aliyun.com
- TLD · .net
- Browse hostnames · hi…
- 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: "hinky.net"})-[: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.