Hostname
soku30.com
Last fetched
soku30.com resolves to 13.112.140.183, announced in 13.112.0.0/14 by AMAZON-02 - Amazon.com, Inc. in JP. soku30.com 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
- 13.112.140.183
- 13.193.0.20
- 13.231.46.145
- 162.159.50.3
162.159.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 18.180.221.89
- 18.181.131.1
- 18.181.149.181
- 18.182.102.65
- 3.115.32.71
- 35.72.231.229
- 35.73.229.241
- 35.73.88.249
- 35.75.246.214
- 35.75.76.240
- 35.76.186.9
- 35.77.140.94
- 35.78.160.215
- 35.79.217.118
- 52.193.64.150
- 52.195.122.207
Attribution
Aws
cloud · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:49
- Registrant organisation
- whois privacy protection service by onamae.com
- Contact emails
- proxy@whoisprotectservice.com
Subdomains
Showing 5 of 9. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-296.awsdns-37.com
- ns-847.awsdns-41.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1359.awsdns-41.org
- ns-1949.awsdns-51.co.uk
MX records
- mail.soku30.com
SPF policy
- ip: 209.85.220.41/32
- include: _spf.google.com
- ip: 103.250.72.120
- ip: 103.250.72.28
- ip: 52.199.4.77
- ip: 54.150.3.6
- ip: 54.238.206.56
- ip: 54.95.133.31
Threat-feed evidence
History
Related pages
Pivot from soku30.com 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: "soku30.com"})-[: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.