Skip to content
Good for Bots

Tea App Checker

teaappchecker.app

Free search tool to check if you have been posted on the Tea dating app

Good for Bots: Good, 86 of 100Get this badge →

On your homepage, it turns this report’s link to teaappchecker.app dofollow.

Scanned

What is Tea App Checker?

Tea App Checker is an online tool designed to help men find out if they have been posted on the Tea app, a dating safety platform built for women where men cannot create accounts to search for themselves. The site allows users to run a search for free by entering a first name, city, and age, or by uploading an optional face photo. Results are typically displayed in about ten seconds, showing potential matches with details such as the photo, name, age, city, post date, and comment or flag counts. While searching and viewing match summaries is free, users must pay a one-time fee per post if they wish to unlock and read the full text and comments.

Through a bot’s eyes

“Tea App Checker is a free search tool that lets men check if they have been posted on the Tea dating app by entering their name, city and age, or a photo.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A language model reading this input learns that Tea App Checker provides external search capabilities for content hosted on the Tea dating safety application. The text covers how the search mechanism works using names, locations, ages, and optional facial recognition, alongside privacy practices like encrypted photo storage and third-party payment processing through Stripe. The homepage and llms.txt provide comprehensive details on what is included in free match results versus unlocked posts, step-by-step guides, policies, and contact information via [email protected]. The provided JSON-LD structured data and llms.txt reiterate the site purpose and supply an FAQ section answering common questions about search duration, privacy, and payment methods. Exact monetary prices for unlocking posts are not explicitly stated in numerical terms on the page, though the text clarifies that prices appear on the unlock button prior to purchase.

Good for Bots report

Tea App Checker scores 86 of 100: the whole readable base, 36 of the 50 agent-layer points, no penalties.

Earned

The whole readable base above the line, 36 of the 50 agent-layer points below it.

86
Penalties0
How scoring works · current methodology →

For the owner of teaappchecker.app

3 prompts, 14 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

50 / 50

Passes.

3.3 of 3.3 points.

robots.txt is valid, with 2 user-agent groups.

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing 13 URLs.

Passes.

8.3 of 8.3 points.

3 of 4 pages read pass. The page at /biometric-notice/ publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Passes.

10 of 10 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.3 of 8.3 points.

11 of 11 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

94 of 94 assessed homepage links and buttons have a nonempty accessible name.

Passes.

2.5 of 2.5 points.

3 of 3 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

110 of 110 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

36.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 13 links across 3 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Passes.

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (25 KB).

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Passes.

5 of 5 points.

States a position on 16 AI crawlers, across 3 purposes (training, search, user-fetch).

Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1919 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 140 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Not established
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://teaappchecker.app/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://teaappchecker.app/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • webzio-extended (ai-training)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://teaappchecker.app/

    https://teaappchecker.app/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

  • Declared allow · robots.txt

    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • duckassistbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • applebot-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)
    • googlebot-image (Unknown)
    • applebot (search, ai-training)
    • duckduckbot (search)
    • anthropic-ai (Unknown)
    • claude-web (Unknown)
    • bytespider (Unknown)
    • cohere-ai (Unknown)
    • youbot (Unknown)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://teaappchecker.app/

    https://teaappchecker.app/robots.txt

    User-agent: googlebot
    User-agent: googlebot-image
    User-agent: bingbot
    User-agent: applebot
    User-agent: duckduckbot
    User-agent: gptbot
    User-agent: oai-searchbot
    User-agent: chatgpt-user
    User-agent: claudebot
    User-agent: claude-user
    User-agent: claude-searchbot
    User-agent: anthropic-ai
    User-agent: claude-web
    User-agent: perplexitybot
    User-agent: perplexity-user
    User-agent: google-extended
    User-agent: applebot-extended
    User-agent: meta-externalagent
    User-agent: meta-externalfetcher
    User-agent: amazonbot
    User-agent: ccbot
    User-agent: bytespider
    User-agent: mistralai-user
    User-agent: cohere-ai
    User-agent: duckassistbot
    User-agent: youbot
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

8th of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 8Tea App Checker · this reportteaappchecker.app

The prompts in the owner view would take Tea App Checker to 100, first in its category.

To the prompts →

Category average 58. The percentile appears once the catalogue holds a few hundred sites.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
5 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
256.1 KB
Took
15.4 s
Homepage
140 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /blog/am-i-on-the-tea-app-how-to-check/article · from the sitemap · read
  • /blog/collection · linked from the homepage · from the sitemap · read
  • /biometric-notice/linked from the homepage · from the sitemap · read

More like Tea App Checker:SaaS & Web AppsSecurity & PrivacyB2C

Same category

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Same category

talhabashir.com

Free online calculators and tools for US taxes, mortgages, business and personal finance

Also Good

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also Good

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Also B2C

submityourstartup.now

Free weekly launch directory where early-stage founders list startups and are ranked by votes

Also B2C

interviewace.online

Real-time AI answer suggestions for job candidates during live video interviews

Do you run teaappchecker.app? Open the owner view → Removing the listing is free. Remove →