Hostname
theappspark.com
Last fetched
theappspark.com resolves to 13.227.192.18, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. theappspark.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.18
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.58
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.78
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.80
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 15.197.225.128
15.197.224.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 3.33.251.168
3.33.240.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
- 99.84.152.20
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.24
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.4
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.67
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for theappspark.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
Subdomains
Showing 2 of 12. View all subdomains →
Mail and authentication
Nameservers
- ns-396.awsdns-49.com
- ns01.domaincontrol.com
- ns02.domaincontrol.com
- ns-706.awsdns-24.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-1086.awsdns-07.org
- ns-1633.awsdns-12.co.uk
MX records
- hzmx01.mxmail.netease.com
- hzmx02.mxmail.netease.com
SPF policy
- include: spf.163.com
Threat-feed evidence
History
Related pages
Pivot from theappspark.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: "theappspark.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.