Hostname
barber-choki.com
Last fetched
barber-choki.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in HU. WHOIS lists iana:1898 as the registrar.
Nutrition Label
Resolution chain
barber-choki.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 |
|---|---|---|---|---|
| 18.172.242.128 | 18.172.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HU |
| 18.172.242.23 | 18.172.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HU |
| 18.172.242.47 | 18.172.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HU |
| 18.172.242.66 | 18.172.240.0/21 | AS16509 | AMAZON-02 - Amazon.com, Inc. | HU |
| 3.165.75.102 | 3.165.75.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 3.165.75.60 | 3.165.75.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 3.165.75.92 | 3.165.75.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
| 3.165.75.95 | 3.165.75.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | SG |
WHOIS identity
- Registrar
- iana:1898
- Organization
- barber choki
- Contact emails
Subdomains
1 observed subdomain of barber-choki.com.
| Subdomain |
|---|
| www.barber-choki.com |
Web-graph footprint
Distinct hostnames that link to or from barber-choki.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for barber-choki.com.
| Mechanism | Target |
|---|---|
| SPF_A | wwwbarber-chokicom.sakura.ne.jp |
| SPF_INCLUDE | _spf.google.com |
| SPF_MX | barber-choki.com |
Related pages
Pivot deeper into the graph from barber-choki.com.
- IP · 18.172.242.128
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:1898
- Country · HU
- Email · pp-domain@app-web.jp
- TLD · .com
- Browse hostnames · ba…
- 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: "barber-choki.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.