Hostname
manaba.jp
Last fetched
manaba.jp resolves to 13.227.192.126, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. manaba.jp 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.227.192.126
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.24
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.35
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.45
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 153.122.81.145
- 18.66.147.106
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.110
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.43
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.147.81
18.66.144.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrant organisation
- asahi net,
- Contact emails
- desk@asahi-net.jp, dotjp-pub@desk.asahi-net.or.jp
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-141.awsdns-17.com
- skyhawk.asahi-net.or.jp
- ns-783.awsdns-33.net
- ns-1304.awsdns-35.org
- ns-1673.awsdns-17.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- ip: 202.224.46.0/24
- include: _spf.google.com
- include: _spf.salesforce.com
- include: _spf.manaba.jp
- include: spf-01.asahi-net.or.jp
- ip: 192.218.247.30
- ip: 192.218.247.32
Threat-feed evidence
History
Related pages
Pivot from manaba.jp 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: "manaba.jp"})-[: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.