Hostname
dataservapp.com
Last fetched
dataservapp.com resolves to 104.21.24.12, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. dataservapp.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
- 104.21.24.12
104.21.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.215.75
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 18.116.121.209
18.116.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.116.75.179
18.116.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.116.95.186
18.116.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.188.21.192
18.188.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.221.177.215
18.220.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 18.222.7.38
18.220.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.146.80.235
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.147.138.122
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.151.155.142
3.144.0.0/13 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.18.196.148
3.16.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 3.20.37.96
3.20.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
- 16.58.102.192
16.58.0.0/17 · AMAZON-02 - Amazon.com, Inc. · Columbus, US
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of dataservapp.com owner
- Contact emails
- d296717e-0859-40d6-8be1-630077f21ccf@identity-protect.org
Subdomains
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- ns-99.awsdns-12.com
- elliot.ns.cloudflare.com
- surina.ns.cloudflare.com
- ns-1004.awsdns-61.net
- ns-1332.awsdns-38.org
- ns-1882.awsdns-43.co.uk
Threat-feed evidence
History
Related pages
Pivot from dataservapp.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: "dataservapp.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.