idealista.com is ranked in the top 1,000 sites and was registered in 1999. We couldn’t read its page: it turned our scanner away.

This site turns automated visitors away, as many large sites do, so we couldn’t read its page. What public records say is below; the score needs the page.

Among the top 1K sites.

A popularity band, not a visit count.

Tranco: #1,263 · Chrome UX Report: Top 1,000 · Majestic Million: #7,301

Each list, with its date
SourceSaysAs of
TrancoA research ranking that combines several traffic and link sources, published daily.#1,263list of 7 Oct 2026
Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly.Top 1,000Aug 2026
Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0#7,301list of 8 Oct 2026

No framework or CMS shows in the page; it uses CDN, Security, DNS, Email and more.

Everything else it uses (14)

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

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

We couldn’t read the page; outside records are below.

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

  • Domain registered21 Aug 1999, 27 years agoNoted
  • HTTPSLoads over HTTPS with a valid certificateFound
  • Security filterNot blocked by Cloudflare’s security filter and Quad9’s security filterNoted
Every signal we looked at

On the site

  • Contact pageBot protection hid the pageCouldn’t check
  • About pageBot protection hid the pageCouldn’t check
  • Privacy policyBot protection hid the pageCouldn’t check
  • TermsBot protection hid the pageCouldn’t check
  • Refund or returns policyBot protection hid the pageCouldn’t check
  • Contact detailsBot protection hid the pageCouldn’t check
  • Company detailsBot protection hid the pageCouldn’t check
  • Payment providersBot protection hid the pageCouldn’t check
  • TrackersBot protection hid the pageCouldn’t check

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 registered21 Aug 1999, 27 years agoNoteddomain registry
  • HTTPSLoads over HTTPS with a valid certificateFound
  • Protective settingsBot protection answered instead of the siteCouldn’t check
  • 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

What it is

Website Summary

We couldn’t read the page, so we can’t say what it is.

We couldn’t read the page, so there are no words of its own to quote.

We couldn’t read the page, so we can’t say what kind of site it is.

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

AI use

  • AI training: doesn’t ask AI training crawlers to stay away.
  • AI assistants: may read it for the people who ask them.

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

Site name
Not given
Language
Not given
What it tells search engines
None

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

Built with AI?

AI Website Detector

We couldn’t read the page, so we couldn’t look for traces.

AI traces: Couldn’t check

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,312 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

Score breakdown

Site Score

No score: we couldn’t read the page, and outside records alone would mislead.

Why each part scored what it did

Domain history

Domain History

Registered in 1999; first archived in 2000.

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

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

  1. 2000: captured
  2. 2001: captured
  3. 2002: captured
  4. 2003: captured
  5. 2004: captured
  6. 2005: captured
  7. 2006: captured
  8. 2007: captured
  9. 2008: captured
  10. 2009: captured
  11. 2010: captured
  12. 2011: captured
  13. 2012: captured
  14. 2013: captured
  15. 2014: captured
  16. 2015: captured
  17. 2016: captured
  18. 2017: captured
  19. 2018: captured
  20. 2019: captured
  21. 2020: captured
  22. 2021: captured
  23. 2022: captured
  24. 2023: captured
  25. 2024: captured
  26. 2025: captured
  27. 2026: captured
Changes, earlier scans and alerts
Since our previous scan
No changes since 10 Oct 2026.
ScannedScoreAI tracesPopularity
shown above—None foundTop 1K
—None foundTop 1K

Findings can change when a site changes or when we update our signatures; each scan keeps the version it used.

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

924 checks on 14 Oct 2026, with version 0.5.0 of our checks and version 1.1 of the score.

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

More sites near it in popularity

Automated findings from the site’s public home page and public records, as of 14 Oct 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.