Website profiles · Technology insights · Alternatives

data.ai

No paid content found
Visit website
Profile views 0 Outbound visits 0 Normal
data.ai Full homepage screenshot

At a glance

Category
Artificial Intelligence
Language
English
Paid-content signal
No paid content foundObserved
Registered
2017
Hosting
amazonaws.comInferred
HTTPS certificate trusted
PassedObserved
Last updated
Unknown

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is data.ai?

data.ai is an app market intelligence service, now part of Sensor Tower. The page at its domain carries a short acquisition notice ("We've Been Acquired by Sensor Tower") alongside links to terms and privacy, which tells you the practical thing a visitor needs to know: the data.ai brand now sits inside a larger analytics company, so current product access, plans and documentation are likely handled through Sensor Tower rather than a standalone data.ai offering.

What it is used for

App market intelligence tools in this category are typically bought to answer questions such as:

  • Market sizing: how large is a category, and which apps are gaining or losing downloads and revenue.
  • Competitive tracking: how a rival app's rankings, estimated revenue or user numbers move after a launch or price change.
  • Store optimization and launch planning: which keywords, markets or ad channels look worth testing.
  • Investment and partnership diligence: whether an app's growth story holds up against third-party estimates.

Typical buyers are mobile product managers, growth and marketing teams, publishers, and analysts at funds or studios. The trade-off is familiar: broad, comparable estimates across many apps and countries, in exchange for figures that are modelled rather than reported by the app makers themselves. Treat any single number as a directional signal and check it against a second source before making a large decision.

A concrete scenario

Suppose you run product for a subscription fitness app and are weighing a launch in two new markets. You would pull category download and revenue trends for both, list the top apps and their recent movement, and compare that with your own store and ad data. Where the third-party estimates and your own figures disagree, that gap is the useful part—it tells you which assumption to test first.

Next step

If you were looking for data.ai's tools, start from Sensor Tower to confirm what is still available under the combined brand, and check whether historical data.ai coverage or contracts carry over before you plan around them.

What happens to my data.ai account and data now that data.ai has been acquired by Sensor Tower?

data.ai now operates as a Sensor Tower company, and the login page states plainly: "We've Been Acquired by Sensor Tower." That tells you the brand and platform are being folded into Sensor Tower's organization, but the page itself does not spell out what happens to individual accounts, saved data, exports or billing. So the practical answer is: expect continuity under a new owner, and confirm the specifics for your account before you rely on it.

What to check, in order

  • Sign-in path: Try your existing data.ai credentials first. If the login redirects to a Sensor Tower sign-in, use the same email address so your history can be matched.
  • Your saved work: Before anything changes, export the reports, dashboards, saved searches and raw data you depend on. Treat exports as your own backup, not as a duplicate of what the vendor keeps.
  • Contract and billing: If you hold a paid plan, check your order form or master agreement for assignment or change-of-control clauses. Ask whether renewal now runs through Sensor Tower and on which terms.
  • Notice of changes: Watch your account email for migration instructions, updated terms of service and privacy notices. The page links to both Terms of Service and Privacy Policy, and those are the documents that govern data handling after a transfer.

A concrete scenario

Suppose your team tracks app rankings in weekly reports built from data.ai dashboards. Two sensible moves: download the last several months of underlying data into your own warehouse now, and ask your account contact whether historical metrics will remain queryable after migration. If the answer is unclear, keep your internal copies as the source of truth until it is confirmed.

Decision criterion

If your work is exploratory and replaceable, waiting for migration instructions is fine. If your work feeds reporting, contracts or compliance, act now: export your data, confirm the contracting entity, and get written confirmation of retention and access terms.

For official updates, check data.ai and Sensor Tower.

How do I log in to data.ai or migrate my access to Sensor Tower?

data.ai is now part of Sensor Tower, so there is no separate data.ai login to migrate. The data.ai page states that it has been acquired by Sensor Tower and identifies data.ai as "a Sensor Tower company." Access to the platform now runs through Sensor Tower accounts rather than a standalone data.ai sign-in.

What this means in practice

  • If you had a data.ai account: expect to reach the same app-market and store intelligence through Sensor Tower's platform, not through a data.ai-branded login page. Any migration of saved reports, watchlists or seat assignments would be handled by Sensor Tower, not by re-registering on data.ai.
  • If you are starting fresh: sign up directly with Sensor Tower and choose the plan that matches your research needs, rather than looking for a data.ai entry point.
  • If you are on a team plan: the person who manages your contract or admin seat is the right contact for account transitions; individual users usually cannot move access on their own.

A useful next step

Before assuming your old credentials work, check whether your organisation already has a Sensor Tower agreement. If it does, ask your admin to add you under that account; if not, compare Sensor Tower's plans against your actual use case — for example, occasional app-store benchmarking versus ongoing competitive tracking across many markets.

For official details, see Sensor Tower and the data.ai notice at data.ai.

What app market intelligence does data.ai provide that I might now find through Sensor Tower?

data.ai's app market intelligence now sits within Sensor Tower, which acquired it. The data.ai page you reached is effectively a handover notice: it states "We've Been Acquired by Sensor Tower" and identifies the site as "data.ai, a Sensor Tower company," pointing visitors onward rather than offering its own product tour. So the practical answer is that the app-market-intelligence capabilities you associate with data.ai are now something to look for in Sensor Tower's offering, and the data.ai login page is no longer the place to start.

What this means in practice

  • New entry point. If you previously used data.ai to size a market, benchmark downloads or revenue, or track competitors' apps, plan to evaluate Sensor Tower for that work instead. The acquisition notice is the clearest signal on the page; it does not itemize which features carried over.
  • Confirm coverage before committing. Because the page gives no feature list, check that the specific metrics and markets you rely on are available in Sensor Tower before migrating a workflow. Treat any assumption that "everything moved unchanged" as unverified.
  • Watch for account and contract changes. Existing data.ai logins and terms may not carry over as-is; the page links to its own Terms of Service and Privacy Policy, so review the current terms rather than assuming continuity.

A concrete scenario

Suppose you run competitive analysis for a mobile game studio and used data.ai to compare category rankings and estimated revenue across regions. The sensible next step is to open Sensor Tower's official site, Sensor Tower, and map each report you used to its equivalent there. If a metric you depended on has no clear match, that gap is your decision criterion for whether to stay, adopt a second source, or change how you report.

How to decide

Your need What to do
Recurring market sizing and competitor tracking Verify equivalents in Sensor Tower before renewing or migrating
A one-off historical comparison Check whether the older data.ai figures remain accessible or must be re-pulled
Contract or data-retention questions Review current terms and confirm with the vendor directly

For broader context on the mobile analytics landscape, Appfigures and Similarweb cover adjacent app and web intelligence needs, though their scope differs from what data.ai offered.

How does data.ai compare with Sensor Tower for app analytics and store data?

data.ai is now part of Sensor Tower, so the two are no longer independent competitors to weigh against each other. The data.ai page states plainly that it has been acquired by Sensor Tower; the practical question is which product line and contract you end up on, not which vendor wins a feature comparison.

What this means for a buyer

  • One vendor, overlapping data. App store rankings, download and revenue estimates, and audience or usage panels were the core of both products. With a single owner, expect consolidation of datasets and tooling over time rather than two rival estimates you can cross-check.
  • Legacy vs. current platform. Existing data.ai subscribers may be migrated to Sensor Tower products or kept on maintained legacy access. Ask specifically which interface, data refresh cadence, and historical coverage your renewal gives you.
  • Pricing and packaging. Neither product publishes simple self-serve pricing for full store intelligence; deals are usually annual and scoped by seats, markets, and modules. Treat any quote as negotiable and tied to your use case.

How to decide

Start from the job, not the brand. If you need broad cross-app market sizing and ad intelligence, ask for a demo of the current Sensor Tower platform and confirm how data.ai-derived metrics are labeled. If your team already has saved dashboards and workflows in data.ai, make continuity of those exports and historical series a written condition of renewal.

Need What to confirm
Historical time series Whether data.ai history carries into the new platform unchanged
Store rankings and estimates Methodology notes and any changes to download/revenue modeling
Team workflows Export formats, API access, seat limits
Budget Multi-year terms, module bundling, migration credits

For independent cross-checks, compare estimates against Similarweb for web and app audience context, or Appfigures for store-level tracking. Use them as sanity checks on methodology, not as replacements for a contracted dataset.

Where can I find data.ai's terms of service and privacy policy after the acquisition?

The terms of service and privacy policy are linked in the footer of the data.ai site, which now carries the notice "We've Been Acquired by Sensor Tower." Look for the "Terms of Service" and "Privacy Policy" links at the bottom of the page at data.ai.

For a practical next step: if you need the policy that governs data you previously provided to data.ai, open both links and check the effective date and the entity named in each document. Post-acquisition sites sometimes route these pages to the acquirer's policies, so confirm whether the text names data.ai, Sensor Tower, or both before relying on it for a contract, procurement review, or data-deletion request. If the footer links are broken or point to a login wall, contact Sensor Tower through its official site at Sensor Tower and ask which entity holds your account data and which policy version applies.

Related questions

More questions →
What is data.ai and what does the site currently offer?

data.ai is an app market intelligence platform that is now part of Sensor Tower. The site currently functions primarily as an acquisition notice and login entry point: its main heading states "We've Been Acquired by Sensor Tower," and the page offers a way to log in along with a link to learn more about the transition. If you are looking for the standalone data.ai product experience, the site no longer presents itself as an independent destination—it identifies itself as "data.ai, a Sensor Tower company."

What the site shows today

The visible content is narrow and transitional rather than a full product marketing site. Based on the page itself, you can expect:

  • An acquisition notice — the prominent heading confirms Sensor Tower has acquired data.ai.
  • A login path — the page is titled "Login," so existing users are directed to sign in rather than browse product features.
  • A "Learn More" link — presumably pointing to information about the acquisition and what it means for users.
  • Standard legal links — Terms of Service and Privacy Policy, with a copyright line reading "© 2026 data.ai, a Sensor Tower company."

What the page does not show: pricing, feature lists, plan comparisons, or a product tour. Any current pricing or packaging details are not stated on this page, so they shouldn't be assumed from it.

What this means if you're a user or evaluator

If you already have an account

The login route is the practical starting point. The page confirms the service continues under the Sensor Tower umbrella, but it does not spell out migration steps, data handling changes, or account continuity on the page itself—those details would sit behind the "Learn More" link or in communications from the company.

If you're evaluating app market intelligence tools

Treat data.ai as part of Sensor Tower's offering rather than a separate product line. For a purchasing decision, you'd want to confirm directly with Sensor Tower which capabilities, data coverage, and contract terms now apply—none of that is documented on this login page.

If you arrived expecting the old data.ai site

The redirect-style experience is expected: the brand persists as a company name, but the site's job has shifted to sign-in and transition messaging.

Quick reference

Question What the site indicates
Is data.ai still independent? No — acquired by Sensor Tower
Can I still log in? Yes, the page is a login entry point
Where do I learn about the transition? Via the "Learn More" link
Are prices or plans listed? Not on this page
Who operates the site now? data.ai, a Sensor Tower company

For anything beyond access and the acquisition itself—feature availability, contracts, or data migration—the reliable next step is the "Learn More" link or direct contact with Sensor Tower, since the page provides no further detail.

How to Log In to Your data.ai Account

data.ai no longer operates as a standalone login destination. The site now states that data.ai has been acquired by Sensor Tower, and the page presents that acquisition notice along with links to learn more, rather than a standard product login flow. If you are trying to reach an existing data.ai account, start by checking whether your access has moved to Sensor Tower and look for migration or support guidance before assuming your old credentials will work at the data.ai address.

What the data.ai site currently shows

The visible page content is limited to the acquisition message:

  • Heading: “We've Been Acquired by Sensor Tower”
  • A “Learn More” link
  • Language selection (English)
  • Footer: “© 2026 data.ai, a Sensor Tower company,” plus Terms of Service and Privacy Policy links

There is no documented login form, username/password field, or account dashboard described in the available page evidence. That matters for planning: the usual “enter email and password” steps cannot be confirmed from the site itself.

Practical steps to regain access

  1. Open data.ai and read the acquisition notice. Confirm you are on the page headed “We've Been Acquired by Sensor Tower.” This tells you the brand is now part of Sensor Tower.
  2. Follow the “Learn More” link. The notice points there for details. Use it to find any stated instructions about accounts, products, or support.
  3. Check Sensor Tower’s own site and support channels. Because data.ai is described as “a Sensor Tower company,” account and product questions are most likely handled there. Look for a help center, contact form, or account migration note.
  4. Try your existing credentials only where a login is actually offered. If you reach a Sensor Tower sign-in page, use the email associated with your data.ai account. If the page does not offer sign-in, do not keep retrying the data.ai URL.
  5. Verify the result. Successful access means you can see your account, subscription, or product data after signing in. If you land on a marketing page or a notice with no form, you have not reached an account entry point.

Common sticking points

  • The page looks like a placeholder. The acquisition notice is the content; a missing login box is expected, not a browser error.
  • Old bookmarks fail. A saved data.ai login URL may now resolve to the notice. Navigate from the main site instead.
  • No pricing or access terms are stated. The available page evidence does not describe plans, free access, or login restrictions, so treat those as unknown until confirmed on Sensor Tower’s pages.
  • Support route is unclear. If “Learn More” does not answer account questions, use Sensor Tower’s contact or help options rather than the data.ai Terms/Privacy links, which cover legal terms, not account recovery.

What to expect

The reliable conclusion from the site is narrow: data.ai is now part of Sensor Tower, and the public page is an acquisition notice. For account access, the workable path is to follow the “Learn More” link and then use Sensor Tower’s support and sign-in surfaces. Confirm any migration instructions there before changing passwords or creating a new account.

Should I keep using data.ai or switch to Sensor Tower?

data.ai is now part of Sensor Tower, and its login page states "We've Been Acquired by Sensor Tower." That makes the decision less about two competing products and more about which entry point and plan fit your needs. If your work depends on data.ai-specific workflows or historical reports, confirm account continuity and data coverage before changing anything. If you mainly need app market intelligence and are open to Sensor Tower's platform, the acquisition likely makes Sensor Tower the natural destination.

What the acquisition changes

The visible signal on data.ai's site is the acquisition notice and a link to learn more. The page does not spell out migration timelines, feature parity, or pricing. Treat those as open items to verify with the vendor rather than assumptions.

What to check first

  • Account continuity: Whether your existing data.ai credentials, saved projects, and exports remain accessible, and whether you need a Sensor Tower account.
  • Data coverage: Whether the metrics, markets, and historical ranges you rely on are available in the combined platform.
  • Contract and billing: How your current subscription, renewal date, and invoicing are handled after the acquisition.
  • Workflow fit: Whether dashboards, alerts, and export formats you use still exist or have equivalents.

data.ai vs. Sensor Tower at a glance

Dimension What to verify
Product status data.ai is described as "a Sensor Tower company" on its own site
Access Login path and whether accounts carry over
Data scope Coverage of apps, markets, and time ranges you need
Reporting Availability of saved reports, exports, and alerts
Commercial terms Plan, renewal, and billing ownership

The table is deliberately a checklist, not a verdict: the source page confirms the acquisition but not the operational details.

How to decide

  1. List your must-haves. Name the specific reports, metrics, and markets your team uses weekly.
  2. Test access. Try logging in through data.ai and note whether you are redirected or asked to create a Sensor Tower account.
  3. Ask the vendor directly. Request written confirmation on account migration, data history, and contract terms.
  4. Run a side-by-side check. Compare one real report in each platform for the same app and market.
  5. Decide on evidence. Keep data.ai if continuity and coverage are confirmed; move if Sensor Tower offers the same data with a workable path.

Common sticking points

  • Assuming the acquisition means automatic migration without confirmation.
  • Comparing headline features instead of the specific metrics your team reports on.
  • Overlooking contract end dates when planning a switch.

For most teams, the practical answer is to verify account and data continuity first, then choose the platform that preserves your existing reporting with the least disruption.

What the Sensor Tower Acquisition Means for data.ai Users

data.ai is now described on its own site as "a Sensor Tower company," following its acquisition by Sensor Tower. For existing users, the practical takeaway is that data.ai's products and accounts now sit within Sensor Tower's organization, so the place to confirm current access, product availability, and any changes is the official data.ai/Sensor Tower properties rather than older documentation. The site does not publish details of plan changes, migration timelines, or account handling on the page reviewed here, so those specifics should be verified directly before you rely on them.

What the site currently states

The data.ai login page carries the heading "We've Been Acquired by Sensor Tower" and links to a "Learn More" page, with the footer identifying the company as "© 2026 data.ai, a Sensor Tower company." That is the extent of the acquisition information visible in the reviewed page content.

What this confirms:

  • The acquisition is acknowledged on data.ai's own site.
  • data.ai continues to be presented as an operating brand under Sensor Tower.
  • A dedicated "Learn More" link exists for official details.

What it does not confirm:

  • Whether any data.ai products are being discontinued, merged, or renamed.
  • Whether pricing, plans, or contract terms change for existing customers.
  • Whether account credentials, saved reports, or historical data remain accessible in the same way.

What this likely means for your account and access

Because the site still presents a login entry point and identifies data.ai as a Sensor Tower company, the reasonable working assumption is that existing users continue to sign in as before unless they are told otherwise. Treat that as a starting point, not a guarantee — the reviewed page does not state that logins, data access, or entitlements are unchanged.

For anyone whose work depends on data.ai data, the safer approach is:

  1. Confirm your access now. Log in through the data.ai login page and check that your workspace, reports, and exports still load as expected.
  2. Check the official "Learn More" page. This is the site's own pointer to acquisition details and is the most direct source for any announced changes.
  3. Watch for account or billing notices. If your organization holds a contract, ask your account contact whether terms, invoicing entity, or renewal process are affected.
  4. Export anything you cannot afford to lose. If you rely on historical reports or saved views, keep local copies until continuity is confirmed in writing.

Where to read official updates

The reviewed page offers one explicit route: the "Learn More" link on the acquisition notice. Beyond that, the site's Terms of Service and Privacy Policy remain linked in the footer and are the place to check for changes to the legal entity handling your data. For product-level announcements, plan changes, or migration guidance, the official data.ai and Sensor Tower channels are the appropriate sources — third-party summaries should be treated as secondary.

Quick reference

Question What the reviewed page supports What to verify elsewhere
Who owns data.ai now? Sensor Tower; data.ai is "a Sensor Tower company" —
Are products or plans changing? Not stated Official "Learn More" page, account notices
Can I still log in? Login page remains live Test your own login and workspace
Is my data affected? Not stated Account contact, official announcements
Where are official updates? "Learn More" link; Terms and Privacy links data.ai and Sensor Tower official channels

If your only question is whether data.ai still exists as a brand you can log in to, the answer from the site is yes — it operates as a Sensor Tower company. If your question is whether your specific plan, data, or contract terms are unchanged, the reviewed page does not answer that, and you should confirm it through the official channels above before making decisions that depend on it.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Registered in 2017, this domain has about 8 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. Registration contact information is publicly available through RDAP. The domain uses the common .ai extension, which is not an independent safety signal.

DNS and Email

The lowest TTL is 60 seconds, supporting rapid record changes at the cost of more frequent lookups. Nameservers are provided by Amazon Route 53, indicating managed DNS hosting. MX records point to the Google Workspace email service. The infrastructure is associated with the amazonaws.com cloud platform. SPF and DMARC are configured. DKIM status is unknown.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Amazon cloud or CDN ecosystem. The certificate is valid for about 197 days in total, with 140 days remaining.

HTTP and Browser Security

The response lacks these common security headers: Referrer-Policy, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header identifies nginx without an exact version. Cookie security attributes are unknown.

Technology Stack Analysis

The public page identifies Next.js, Google Tag Manager, nginx without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 15 characters, within a common display range. The observed directives allow indexing and link following. No Generator meta tag is publicly exposed.

Hosting and Email

DNSAmazon Route 53
Hostingamazonaws.com
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagAshburn, Virginia, United States Inferred 44.197.57.129

Registration details

RDAP / WHOIS

Registrar101domain GRS Limited
Registered2017-12-15
Expires2028-05-03
Domain statusclient transfer prohibited
Nameserversns-1244.awsdns-27.org、ns-1768.awsdns-29.co.uk、ns-188.awsdns-23.com、ns-891.awsdns-47.net
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aalb-dca-aa-p-eng-1-1734375314.us-east-1.elb.amazonaws.com44.197.57.12960—
Aalb-dca-aa-p-eng-1-1734375314.us-east-1.elb.amazonaws.com52.86.240.1860—
MXdata.aiaspmx.l.google.com601
MXdata.aialt1.aspmx.l.google.com605
MXdata.aialt2.aspmx.l.google.com605
MXdata.aialt3.aspmx.l.google.com6010
MXdata.aialt4.aspmx.l.google.com6010
NSdata.ains-1244.awsdns-27.org172800—
NSdata.ains-1768.awsdns-29.co.uk172800—
NSdata.ains-188.awsdns-23.com172800—
NSdata.ains-891.awsdns-47.net172800—
TXTdata.aiMS=6AAE49D912F714BEDA12920B219B52CEA993C74E300—
TXTdata.aiMS=D9627373C23B2468A6530B1CF69F8637A274BA1A300—
TXTdata.aiMS=ms61207149300—
TXTdata.aiZOOM_verify_GH0fD4PKUDIJZ4iPxWSfHx300—
TXTdata.aiatlassian-domain-verification=3alvWaJyUQgnaOEvmUDIYoCq4e8yAHts5vEHfF3bBL5gxaKzJOdWvv7ETTkXfWta300—
TXTdata.aidocusign=8c73fe02-103d-4a40-ad6d-c055829a8025300—
TXTdata.aidrift-domain-verification=5918da6718cb0f3c162261324abce42769f6c168d200293ea5baafd22575db46300—
TXTdata.aigoogle-site-verification=CwmLB-FGIbSLEz9XbabgdX0G0l6RBzJ_UZ4UnpgBwDA300—
TXTdata.aigoogle-site-verification=LdqEl6MGai9uGYYmDUureDgMLzNNQbAerzIAupGAOXw300—
TXTdata.aigoogle-site-verification=Ugdpspvf5BNwLX1MzurpFCdeAjJqTWhD_4JxcIRwooQ300—
TXTdata.aigoogle-site-verification=ftI3WO3BKOvMwt5YUhDKaBzTyML156rNZDd-Krz8cOU300—
TXTdata.aigoogle-site-verification=ilTTKjpi1aPrhQiNRhY3_kcmOVvduCaPcQnSzZB092Q300—
TXTdata.aiivtoaepff22bv2tidqd8duff7i300—
TXTdata.aiv=spf1 include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com include:_spf.salesforce.com include:mktomail.com include:mail.zendesk.com include:spf.mandrillapp.com include:spf.data.ai ~all300—
TXTdata.aiw8q3clrzgh0jng8nrgjyg29kn4l6nj57300—
TXTdata.aiyandex-verification: 9078489aae66d4c8300—
CNAMEwww.data.aialb-dca-aa-p-eng-1-1734375314.us-east-1.elb.amazonaws.com300—
DMARC_dmarc.data.aiv=DMARC1; p=quarantine; rua=mailto:[email protected]300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2
Negotiated protocolTLSv1.2
Certificate subject*.data.ai
IssuerAmazon
Valid until2027-03-07T23:59 · Remaining when checked: 140 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlno-store
servernginx
strict-transport-securitymax-age=31536000
content-security-policydefault-src * data: blob: ;script-src * 'self' 'unsafe-inline' 'unsafe-eval' ;worker-src * blob: ;style-src * 'unsafe-inline' data: ;frame-ancestors 'self' static-s.aa-cdn.net *.appannie.com *.appannie.com.cn *.data.ai *.appannie.org *.sharepoint.com *.officeapps.live.com https://onedrive.live.com rise.articulate.com scorm.thoughtindustries.com ;img-src * data: blob: ;font-src * data: ;media-src * data: blob: ;base-uri 'self' d6tizftlrpuof.cloudfront.net manifest.prod.boltdns.net secure.brightcove.com ;connect-src * data: blob: wss://api.appcues.net;
x-frame-optionsSAMEORIGIN
x-content-type-optionsnosniff
set-cookieRedacted

Identified technologies

Next.jsGoogle Tag Managernginx

Pages, Search and Sharing

Meta descriptionNot detected
Canonical URLhttps://www.data.ai/account/login/
LanguageEnglish (default)
Twitter CardNot detected

Unknown

All bots 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 5 seconds
googlebot 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 2 seconds
bingbot 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 2 seconds
coccoc 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 10 seconds
jikespider 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 10 seconds
ahrefsbot 0 allowed · 1 disallowed
  • Disallow/
baiduspider 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 2 seconds
360spider 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 2 seconds
sogouspider 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 2 seconds
yisouspider 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 2 seconds
sosospider 0 allowed · 21 disallowed
  • Disallow/top/*date=
  • Disallow/matrix/*date=
  • Disallow/search/*
  • Disallow/search_ac/
  • Disallow*/ranking_table/
  • Disallow*/features/table/
  • Disallow*/rank-chart/
  • Disallow/top-table/*
  • Disallow/matrix-table/*
  • Disallow/apps/*/top/*date=
  • Disallow/apps/*/matrix/*date=
  • Disallow/apps/*/top-table/*
  • Disallow/apps/*/matrix-table/*
  • Disallow/areyouhuman
  • Disallow/company/*
  • Disallow/apps/all-stores/app/*
  • Disallow/apps/all-stores/franchise/*
  • Disallow*/keyword-top-data/
  • Disallow*/keywords-rank/
  • Disallow/media/legal/*
  • Disallow/account/password-reset/*
  • IntervalCrawl delay 2 seconds

Recent Updates

  • Website images
  • Screenshots
  • Network details
  • Website Technologies
  • Pages and Search Information
  • HTTP Response Information
  • TLS and certificates
  • Website profile
  • Website Name

User reviews (0)

  • No reviews yet.