Hostname
bot.lionmoby.com
Last fetched
bot.lionmoby.com resolves to 13.227.192.117, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. bot.lionmoby.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.227.192.117
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.27
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.70
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.83
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.249.126.119
13.249.120.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 13.249.126.20
13.249.120.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 13.249.126.24
13.249.120.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 13.249.126.64
13.249.120.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 3.161.82.11
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.111
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.21
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.6
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for bot.lionmoby.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bot.lionmoby.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns-280.awsdns-35.com
- ns-566.awsdns-06.net
- ns-1027.awsdns-00.org
- ns-1828.awsdns-36.co.uk
Threat-feed evidence
History
Related pages
Pivot from bot.lionmoby.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: "bot.lionmoby.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.