Scan a site

Libelle.nl

libelle.nl

Scanned Fresh936 checks

100of 100
How it adds up →
In its own wordsLibelle - Leef leukerBij Libelle lees je mooie persoonlijke verhalen en bijzondere interviews die je raken. Wij brengen elke dag het laatste entertainmentnieuws en alles wat je wilt weten over gezondheid, geld, lifestyle en horoscopen.
PopularityTop 10KBuilt withContentful, Next.js12 technologies foundTrust signals6 of 7 foundDomain registered 29 years agoBuilt with AI? None foundNo traces found

libelle.nl is ranked in the top 10,000 sites and was registered in 1997. It is built with Contentful and Next.js; we found no traces of an AI site builder.

Popularity

Website Traffic Checker

Among the top 10K sites.

A popularity band, not a visit count.

Tranco: #18,882 · Chrome UX Report: Top 10,000 · Majestic Million: #47,139

Each list, with its date
SourceSaysAs of
TrancoA research ranking that combines several traffic and link sources, published daily.#18,882list of 27 Oct 2026
Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly.Top 10,000Sep 2026
Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0#47,139list of 28 Oct 2026
Was this answer right?

Technology

Tech Stack Checker

Built with Contentful and Next.js.

  • ContentfulCMSShow evidenceHide evidence
    Evidence · page source, line 3121
    …avaert", "url": "https://images.ctfassets.net/765y2hpj99ul/3wriNBuIKCjyTJmIV4CkQY/686…
    Popular sites using Contentful Is this wrong? Report it
  • Next.jsFrameworkShow evidenceHide evidence
    Evidence · page source, line 1
    <script src="/_next/static/chunks/1dc7vm0aoemiv.js">
    Popular sites using Next.js Is this wrong? Report it
Everything else it uses (10)

Around it: CDN, DNS, Email, SEO and more.

Business tools can stay listed after a site stops using them.

Was this answer right?

Trust signals

Website Trust Checker

6 of 7 trust signals found on the home page.

Signals, not a judgement: missing details are common on small, honest sites.

  • Domain registered25 Apr 1997, 29 years agoNoted
  • HTTPSLoads over HTTPS with a valid certificateFound
  • Contact detailsIn structured dataFound
    Show evidenceHide evidence
    Exhibit 1 · page source, line 3121Masked for privacy. An email address or phone number can belong to a person, and data protection law, such as the EU’s GDPR, asks us to keep only what we need: that the page lists one, and where.
    "telephone": "+31 •••-•• •• •13"
    Is this wrong? Report it
  • Privacy policyLinked from the home pageFound
  • TermsLinked from the home page, and the page opensFound
  • Security filterNot blocked by Cloudflare’s security filter and Quad9’s security filterNoted
Every signal we looked at

On the site

  • Contact pageLinked from the home pageFound
  • About pageLinked from the home page, and the page opensFound
  • Privacy policyLinked from the home pageFound
  • TermsLinked from the home page, and the page opensFound
  • Refund or returns policyNo link found on the home pageNot found
  • Contact detailsIn structured dataFound
    Show evidenceHide evidence
    Exhibit 1 · page source, line 3121Masked for privacy. An email address or phone number can belong to a person, and data protection law, such as the EU’s GDPR, asks us to keep only what we need: that the page lists one, and where.
    "telephone": "+31 •••-•• •• •13"
    Is this wrong? Report it
  • Company detailsName: Libelle, address givenFound
  • Payment providersNone on the home pageNoted
  • TrackersNone found on the home pageNoted

Behind the site

  • Security filterNot blocked by Cloudflare’s security filter and Quad9’s security filterNotedCloudflare’s security filter and Quad9’s security filter
  • Domain registered25 Apr 1997, 29 years agoNoteddomain registry
  • HTTPSLoads over HTTPS with a valid certificateFound
  • Protective settings5 of 6 in placeFound
  • Email protectionProtected against forged emailFoundDNS records

A second opinion on its security setup: Mozilla’s HTTP Observatory grades the site when you open it. Ten checks before you buy · A signal looks wrong? Report it

Was this answer right?

What it is

Website Summary

It calls itself “Libelle - Leef leuker”.

In its own wordsLibelle - Leef leukerBij Libelle lees je mooie persoonlijke verhalen en bijzondere interviews die je raken. Wij brengen elke dag het laatste entertainmentnieuws en alles wat je wilt weten over gezondheid, geld, lifestyle en horoscopen.

The page doesn’t show enough to say what kind of site it is (a shop, a blog, an app…).

Who is behind it

  • structured dataLibelle
  • copyright lineDPG Media B.V
  • WikidataLibelle

Confirmed by 2 independent sources: structured data and Wikidata.

Show evidence (3)Hide evidence
Exhibit 1 · page source, line 3121
"name": "Libelle"
Exhibit 2 · page source, line 4726
© 2026 DPG Media B.V. - Alle rechten voorbehouden
Exhibit 3 · Wikidata
Q5209146: Libelle
Is this wrong? Report it

Each name is quoted from its source. A brand and the company that owns it often go by different names.

More about it: Wikidata, profiles, AI use, page facts

In Wikidata

  • Libelle: Dutch magazine · periodical · since 1934

Wikidata, the free knowledge base behind Wikipedia, lists this domain as the official website of this item. Volunteers write it; each item shows its sources.

Find them on

The profiles its home page links. We haven’t checked who runs them.

AI use

  • AI training: asks Amazonbot, Applebot-Extended, Bytespider, ClaudeBot and 17 more to stay away.
  • AI assistants: asks meta-externalfetcher, ChatGPT-User, PerplexityBot, MistralAI-User and 10 more to stay away.
Show evidence (35)Hide evidence
Exhibit 1 · robots.txt, line 1
User-Agent: Amazonbot · Disallow: /
Exhibit 2 · robots.txt, line 4
User-Agent: Applebot-Extended · Disallow: /
Exhibit 3 · robots.txt, line 7
User-Agent: Bytespider · Disallow: /
Exhibit 4 · robots.txt, line 10
User-Agent: ClaudeBot · Disallow: /
Exhibit 5 · robots.txt, line 13
User-Agent: Claude-Web · Disallow: /
Exhibit 6 · robots.txt, line 16
User-Agent: cohere-ai · Disallow: /
Exhibit 7 · robots.txt, line 19
User-Agent: Diffbot · Disallow: /
Exhibit 8 · robots.txt, line 22
User-Agent: Google-Extended · Disallow: /
Exhibit 9 · robots.txt, line 28
User-Agent: GPTBot · Disallow: /
Exhibit 10 · robots.txt, line 34
User-Agent: anthropic-ai · Disallow: /
Exhibit 11 · robots.txt, line 43
User-Agent: CCBot · Disallow: /
Exhibit 12 · robots.txt, line 46
User-Agent: YouBot · Disallow: /
Exhibit 13 · robots.txt, line 49
User-Agent: DeepSeekBot · Disallow: /
Exhibit 14 · robots.txt, line 61
User-Agent: Timpibot · Disallow: /
Exhibit 15 · robots.txt, line 82
User-Agent: icc-crawler · Disallow: /
Exhibit 16 · robots.txt, line 91
User-Agent: cotoyogi · Disallow: /
Exhibit 17 · robots.txt, line 103
User-Agent: meta-externalagent · Disallow: /
Exhibit 18 · robots.txt, line 124
User-Agent: PanguBot · Disallow: /
Exhibit 19 · robots.txt, line 130
User-Agent: TikTokSpider · Disallow: /
Exhibit 20 · robots.txt, line 139
User-Agent: VelenPublicWebCrawler · Disallow: /
Exhibit 21 · robots.txt, line 151
User-Agent: AI2Bot · Disallow: /
Exhibit 22 · robots.txt, line 25
User-Agent: Meta-ExternalFetcher · Disallow: /
Exhibit 23 · robots.txt, line 31
User-Agent: ChatGPT-User · Disallow: /
Exhibit 24 · robots.txt, line 37
User-Agent: PerplexityBot · Disallow: /
Exhibit 25 · robots.txt, line 52
User-Agent: MistralAI-User · Disallow: /
Exhibit 26 · robots.txt, line 64
User-Agent: YandexAdditional · Disallow: /
Exhibit 27 · robots.txt, line 67
User-Agent: YandexAdditionalBot · Disallow: /
Exhibit 28 · robots.txt, line 76
User-Agent: Perplexity-User · Disallow: /
Exhibit 29 · robots.txt, line 94
User-Agent: Amzn-SearchBot · Disallow: /
Exhibit 30 · robots.txt, line 97
User-Agent: Claude-User · Disallow: /
Exhibit 31 · robots.txt, line 100
User-Agent: Amzn-User · Disallow: /
Exhibit 32 · robots.txt, line 133
User-Agent: DuckAssistBot · Disallow: /
Exhibit 33 · robots.txt, line 136
User-Agent: meta-webindexer · Disallow: /
Exhibit 34 · robots.txt, line 163
User-Agent: Claude-SearchBot · Disallow: /
Exhibit 35 · robots.txt, line 166
User-Agent: OAI-SearchBot · Disallow: /
Is this wrong? Report it

What its robots.txt and robots tags ask of AI crawlers. Each crawler chooses whether to follow it.

Site name
Libelle.nl
Language
Dutch (nl)
What it tells search engines
Organization, BreadcrumbList, WebPage, CollectionPage, ItemList

Named in its structured data

  • OrganizationLibelleAmsterdam, NL
  • OrganizationDPG Media B.V.Amsterdam, NL

Read from what the page says about itself; we haven’t checked whether it’s true.

Was this answer right?

Built with AI?

AI Website Detector

No AI builder traces found.

We look for what AI site builders such as Lovable, Bolt and v0 leave in a page. Code written with an AI assistant such as Cursor, Claude Code or ChatGPT leaves nothing to find, so we can’t tell whether AI helped.

AI traces: None found

How we know

AI site builders leave traces in the sites they make. We look for the traces of 53 of them and show every match with the line it came from, so you can check it yourself.

We test this on 2,275 sites whose makers we know, and publish what we get wrong.

How we test it · Every builder we know · How to tell if a site was built with AI

Was this answer right?

AI access

AI Crawler Checker

Ready for AI: it scores 82 of 100.

It keeps 35 of 51 AI crawlers out, for training and for answers: the site’s choice, never scored.

82of 100

AI readiness

AI-friendly

It says what it is in structured data and lists its pages.

  1. Findable
  2. Readable
  3. AI-friendly

To reach Agent-ready:Files for AI agents +10

Can AI find it?

30/32

Can AI read it?

52/58

Can agents use it?

0/10

Optional: for sites with an API or a sign-in.

Higher than 56% of the 2,439 most visited sites we read, whose median is 72.

Checked 1 Nov 2026

What to fix

Optional: 4 fixes few sites have yetup to +18 points

  • Files for AI agents

    Now None of the 8 we look for.

    If agents could use the site, publish what they need where they look.

    Details

    Why it matters: Agents act for people: they look for these files to know what a site lets them do. Worth it only if agents can use the site.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    If AI agents could use https://www.libelle.nl for its visitors (to search it, book, buy or sign in), publish what they need at the standard addresses, and only what the site really offers: an MCP server card at /.well-known/mcp/server-card.json if it runs an MCP server, an API catalog at /.well-known/api-catalog (RFC 9727) listing its public APIs, and OAuth protected resource metadata at /.well-known/oauth-protected-resource (RFC 9728) if agents sign in.
    +10optional

  • llms.txt

    Now None found.

    Publish a short Markdown summary of the site at /llms.txt.

    Details

    Why it matters: A short summary for AI models, at an address they can find. A proposal: few AI companies say they read it yet.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    Create https://www.libelle.nl/llms.txt as llmstxt.org describes it: a Markdown file with an H1 naming the site, a one-paragraph summary in a blockquote, and short sections listing its most useful pages as links, each with a line on what it holds. Serve it as text/plain or text/markdown.
    +4optional

  • Markdown copy

    Now Not offered: it sends the page’s HTML.

    Answer requests for Markdown with a Markdown version of the page.

    Details

    Why it matters: A Markdown copy gives AI tools the page’s words without the HTML around them.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    When a request to https://www.libelle.nl asks for Markdown (its Accept header includes text/markdown), answer with a Markdown version of the page’s main content and the header Content-Type: text/markdown. Requests for HTML keep getting HTML; add Vary: Accept so caches keep the two apart.
    +2optional
Every check, with its evidence

Can AI find it?

  • robots.txtFound, 132 linesFound
  • SitemapListed in robots.txt, and it lists 113 sitemapsFound
    Show evidenceHide evidence
    Exhibit 1 · robots.txt, line 176
    Sitemap: https://www.libelle.nl/sitemap.xml
    Is this wrong? Report it
  • Links for AI toolsNone in the home page’s headersNot found
  • Search listingAllowed: no noindex ruleAllowed

Can AI read it?

  • Text without scripts8,374 characters before scripts runFound
    Show evidenceHide evidence
    Exhibit 1 · page text, before scripts run
    Libelle - Leef leuker Ga naar de inhoud Club Series Magazine Persoonlijk Lifestyle Puzzels Club Series Magazine Persoonlijk Lifestyle Puzzels Series Libelle Club Columnisten Persoonlijk Royal…
    Is this wrong? Report it
  • Markdown copyNot offered: it sends the page’s HTMLNot found
  • llms.txtNone foundNot found
  • Title and descriptionBothFound
    Show evidence (2)Hide evidence
    Exhibit 1 · page source, line 1
    <title>Libelle - Leef leuker</title>
    Exhibit 2 · page source, line 1
    <meta name="description" content="Bij Libelle lees je mooie persoonlijke verhalen en bijzondere interviews die je raken. Wij brengen elke dag het laatste entertainmentnieuws en alles wat je wilt weten over gezondheid, geld, lifestyle…">
    Is this wrong? Report it
  • Structured dataFound: Organization, BreadcrumbList, WebPage and 2 moreFound
    Show evidenceHide evidence
    Exhibit 1 · page source, line 3121
    <script type="application/ld+json">
    Is this wrong? Report it

Can agents use it?

  • API catalogNone foundNot found
  • Sign-in for AI agentsNone foundNot found
  • Auth.mdNone foundNot found
  • AI catalogNone foundNot found
  • MCP serverNone foundNot found
  • Agent cardNone foundNot found
  • Agent SkillsNone foundNot found
  • Agents in DNSNone foundNot found

What it lets AI do

Not scored

Keeping AI out is the site’s choice, so it never lowers the score.

  • AI trainingOpenAI, Anthropic, Google, Apple and 3 more kept out, Meta partlyPartly
  • AI answers and searchOpenAI, Anthropic, Perplexity, Meta and 2 more kept out; the rest let inPartly
Every AI crawler, and how we checked

AI companies

  • OpenAIChatGPTTo train its modelsKept outGPTBotline 28To answer people and searchKept outOAI-SearchBotline 166ChatGPT-Userline 31
  • AnthropicClaudeTo train its modelsKept outClaudeBotline 10anthropic-ailine 34Claude-Webline 13To answer people and searchKept outClaude-SearchBotline 163Claude-Userline 97
  • GoogleGeminiTo train its modelsKept outGoogle-Extendedline 22To answer people and searchLet inGoogle-CloudVertexBot
  • PerplexityTo train its modelsNone namedTo answer people and searchKept outPerplexityBotline 37Perplexity-Userline 76
  • MetaMeta AITo train its modelsPartlymeta-externalagentline 103, kept outFacebookBotlet inTo answer people and searchKept outmeta-externalfetcherline 25meta-webindexerline 136
  • AppleApple IntelligenceTo train its modelsKept outApplebot-Extendedline 4To answer people and searchNone named
  • AmazonTo train its modelsKept outAmazonbotline 1To answer people and searchKept outAmzn-SearchBotline 94Amzn-Userline 100
  • Common Crawlopen data for trainingTo train its modelsKept outCCBotline 43To answer people and searchNone named
  • ByteDanceTo train its modelsKept outBytespiderline 7TikTokSpiderline 130To answer people and searchNone named
  • MistralLe ChatTo train its modelsNone namedTo answer people and searchKept outMistralAI-Userline 52

13 of the 27 other AI crawlers we know are kept out: cohere-ai, Diffbot, Timpibot, AI2Bot, YouBot and 8 more.

What it tells AI crawlers

It gives no Content Signals and no “noai” tag.

Like 30% of the 408 popular sites whose robots.txt we’ve read since 29 Oct 2026, it keeps at least one AI training crawler out. Of the 517 popular sites we’ve checked since 29 Oct 2026, 9% have a page drawn by scripts, 2% send a Markdown copy, 9% have an llms.txt and 3% offer a file for AI agents. How many websites block AI crawlers?

We read the site once, as our named bot: its robots.txt, read as crawlers read it, its home page and the files AI tools ask sites for. What we couldn’t read says so. robots.txt asks and doesn’t enforce: a firewall can treat AI crawlers differently from us.

Was this answer right?

Score breakdown

Site Score

100 of 100: strong trust signals.

How established and checkable it is; AI traces carry no weight.

100of 100
TransparencyContact, policies and about page30 / 30
Track recordHow long the domain has existed25 / 25
PopularityIts place in public rankings20 / 20
Security and setupHTTPS and standard protections15 / 15
ConsistencyName, description and what it tells search engines10 / 10
Why each part scored what it did
TransparencyContact, policies and about page30 / 30contact page linked · email and phone given · privacy policy linked · terms linked · no payments seen, so no refund policy needed · about page linked
Track recordHow long the domain has existed25 / 25domain registered 29 years ago
PopularityIts place in public rankings20 / 20Top 10K in a popularity list
Security and setupHTTPS and standard protections15 / 15loads over HTTPS · sends visitors to HTTPS · always uses HTTPS · protective settings
ConsistencyName, description and what it tells search engines10 / 10site name matches the domain · describes itself · tells search engines what it is

A high score isn’t a promise that a business is honest. How the score works.

Was this answer right?

Domain history

Domain History

Registered in 1997; first archived in 1998.

  1. Domain registeredRDAP
  2. First captured by the web archiveInternet Archive
  3. This scanCheckAnySite

In the web archive: captured in 28 of 29 years · see the first capture

  1. 1998: captured
  2. 1999: captured
  3. 2000: captured
  4. 2001: captured
  5. 2002: captured
  6. 2003: captured
  7. 2004: captured
  8. 2005: captured
  9. 2006: captured
  10. 2007: captured
  11. 2008: captured
  12. 2009: no capture
  13. 2010: captured
  14. 2011: captured
  15. 2012: captured
  16. 2013: captured
  17. 2014: captured
  18. 2015: captured
  19. 2016: captured
  20. 2017: captured
  21. 2018: captured
  22. 2019: captured
  23. 2020: captured
  24. 2021: captured
  25. 2022: captured
  26. 2023: captured
  27. 2024: captured
  28. 2025: captured
  29. 2026: captured
Changes, earlier scans and alerts
Since our previous scan
This is our first scan of the site.
Was this answer right?

How we scanned it

Only from what anyone can see: the site’s public pages and public records.

  • Politely. Our scanner, CheckAnySiteBot, says who it is and follows the site’s robots.txt.
  • With sources. Every fact above says where it came from and when.
  • Without guessing. When we couldn’t check something, we say so.
This scan, in numbers

936 checks on 1 Nov 2026, with version 0.6.0 of our checks and version 1.1 of the score.

How we work · What each version changed · About our scanner

Quick look

Built with AI?

None foundWe found no AI builder traces.

“None found” never means “made by a person”: coding assistants leave no traces.

All the evidence →

Related

Quick look

How popular is it?

Top 10KBy the best of 3 public lists.

  • Tranco#18,882list of 27 Oct 2026
  • Chrome UX ReportTop 10,000Sep 2026
  • Majestic Million#47,139list of 28 Oct 2026

A popularity band, never a visit count.

The popularity section →

Related

Quick look

What is it built with?

CMS
Contentful
Framework
Next.js

And 10 more around it (CDN, DNS, Email, SEO), in the section.

Each with its evidence →

Related

Quick look

Which trust signals does it show?

On the site

  • Contact pageFound
  • About pageFound
  • Privacy policyFound
  • TermsFound
  • Refund or returns policyNot found
  • Contact detailsFound
  • Company detailsFound
  • Payment providersNoted
  • TrackersNoted

Behind the site

  • Security filterNoted
  • Domain registeredNoted
  • HTTPSFound
  • Security headersFound
  • Software versionsNoted
  • NetworkNoted
  • Email setupFound
  • First certificateCouldn’t check
  • DNSSECFound
  • Certificate authoritiesNot found
  • Security contactFound

Signals, not a judgement: missing details are common on small, honest sites.

Every signal with its source →

Related

How has it changed? →
Quick look

How does it add up?

100of 100

Strong trust signals. An open formula (v1.1): every point comes from a finding above. AI traces carry no weight.

TransparencyContact, policies and about page30 / 30
Track recordHow long the domain has existed25 / 25
PopularityIts place in public rankings20 / 20
Security and setupHTTPS and standard protections15 / 15
ConsistencyName, description and what it tells search engines10 / 10
Why each part scored what it did →

Related

Questions about libelle.nl

What is libelle.nl?

libelle.nl describes itself: “Bij Libelle lees je mooie persoonlijke verhalen en bijzondere interviews die je raken. Wij brengen elke dag het laatste entertainmentnieuws en alles wat je wilt weten over gezondheid, geld, lifestyle…” See the evidence

How old is libelle.nl?

Its domain was registered on 25 Apr 1997, 29 years ago. See the evidence

What is libelle.nl built with?

It is built with Contentful and Next.js; we found 12 technologies in all. See the evidence

How popular is libelle.nl?

It is among the top 10,000 sites, by Tranco, Chrome UX Report and Majestic Million. See the evidence

Was libelle.nl made with AI?

We found no traces of an AI site builder. That doesn’t prove a person built it: AI coding assistants leave no traces. See the evidence

Who is behind libelle.nl?

Libelle, named by its structured data and Wikidata. See the evidence

More sites near it in popularity

Automated findings from the site’s public home page and public records, as of 1 Nov 2026. They describe what we found, not the people or business behind the site, and they may be incomplete or out of date. This is information, not advice. Terms · Report an error

What this scan can’t tell you
  • Whether the business is real, honest or delivers what it sells.
  • Whether a site was made with AI when no traces were left: coding assistants and hand edits leave none.
  • How many people visit: we show popularity bands from public lists, not visits.
  • Anything beyond the home page as it was at the time of the scan.

Is this your site? Ask for a correction.

Share this result

Share libelle.nl

The result describes what we found on 1 Nov 2026, with evidence.

Side by side

Compare with another site

AI traces, popularity, trust signals and the score, side by side.

Free scan · no sign-up

What do you want to find out?

Or check one thing:

Trywikipedia.orgstripe.combbc.co.uk

One scan answers everything: AI traces, popularity, technology, trust signals, how the site describes itself, a score and its history. A quick check only decides which answer comes first. We read public pages as CheckAnySiteBot and follow robots.txt.