Hostname
askajumma.com
Last fetched
askajumma.com resolves to 15 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in KR. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
askajumma.com resolves to 15 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 3.5.185.62 | 3.5.184.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.186.170 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.100 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.103 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.35 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.43 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.52 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.6 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.187.76 | 3.5.186.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.189.123 | 3.5.188.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.189.48 | 3.5.188.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.189.71 | 3.5.188.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 3.5.189.98 | 3.5.188.0/23 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 52.219.146.80 | 52.219.146.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
| 52.219.60.129 | 52.219.60.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | KR |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of askajumma.com owner
- Contact emails
Subdomains
1 observed subdomain of askajumma.com.
| Subdomain |
|---|
| www.askajumma.com |
Threat posture
History
Mail and authentication
MX records
SPF policy
1 SPF mechanism authorising senders for askajumma.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.google.com |
Related pages
Pivot deeper into the graph from askajumma.com.
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "askajumma.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.