Hostname
imada-connected.com
Last fetched
imada-connected.com resolves to 6 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in JP. WHOIS lists iana:1557 as the registrar.
Nutrition Label
Resolution chain
imada-connected.com resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 13.159.221.41 | 13.158.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 13.159.223.134 | 13.158.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 3.115.227.25 | 3.112.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 54.150.143.47 | 54.150.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 54.248.144.10 | 54.248.128.0/17 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
| 57.181.124.41 | 57.180.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | JP |
WHOIS identity
- Registrar
- iana:1557
- Organization
- xserver
- Contact emails
Subdomains
1 observed subdomain of imada-connected.com.
| Subdomain |
|---|
| www.imada-connected.com |
Web-graph footprint
Distinct hostnames that link to or from imada-connected.com in the public web crawl.
2 sites linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
6 SPF mechanisms authorising senders for imada-connected.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | one.zoho.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | zcsend.net |
| SPF_INCLUDE | zoho.jp |
| SPF_IP | 18.176.6.87/32 |
| SPF_MX | imada-connected.com |
Related pages
Pivot deeper into the graph from imada-connected.com.
- IP · 13.159.221.41
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:1557
- Country · JP
- Email · info@xserver.co.jp
- TLD · .com
- Browse hostnames · im…
- 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: "imada-connected.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.