elespectador.com — domain analysis

200HTTP status

212msResponse time

3,494Words on the homepage

4/6Security headers set

What is elespectador.com about?

The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:

• redacci ×29
• 04-10-2026 ×27
• publicidad ×26
• para ×22
• colombia ×21
• suscriptores ×18
• bibo ×16
• deportes ×15
• bogot ×14
• mundo ×12

Does elespectador.com publish the usual trust pages?

None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.

These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.

How does elespectador.com compare with other domains analysed here?

Measured against the 83 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.

Related domains in this index

Analysed domains built on a similar stack:

• alison.com
• beautypura.com
• casei.com
• casesindia.com
• diariolibre.com
• eduten.com
• emaktabkundalik.com
• farmersonly.com

Other analysed domains served from the same country:

• centre.com
• cleartrip.com
• halk.com
• homedepot.com
• insta.com
• joinmyquiz.com
• nasyonal.com
• poke.com

When was elespectador.com registered?

elespectador.com was registered on 29 February 1996, which makes it about 30 years old.

A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.

The registrar of record is Network Solutions, LLC.

Registration runs until 2 March 2028.

The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.

Where is elespectador.com hosted?

The first address resolves to infrastructure in San Francisco, United States.

The network is operated by Automattic, Inc (AS2635 Automattic, Inc).

Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.

What is elespectador.com running on?

elespectador.com exposes 3 identifiable technologies: WordPress, Google Tag Manager, X-Powered-By: WordPress VIP <https://wpvip.com>.

WordPress is identifiable from its asset paths, so the platform is public knowledge regardless of whether the version is hidden. That matters mainly for patching discipline: known-platform sites are scanned automatically and constantly.

Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.

• WordPress
• Google Tag Manager
• X-Powered-By: WordPress VIP <https://wpvip.com>

The page declares a generator of WordPress 7.1.2.

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

At 212ms to first byte this response is unremarkable for a homepage measured from a single European location.

The HTML alone is 559KB before images, stylesheets or scripts are counted, which is heavy for a document that browsers must parse before anything renders.

The HTML is compressed with gzip.

What does the homepage say about itself?

The title runs to 78 characters, so search results will truncate it and the end of the sentence will not be read.

A meta description of 153 characters is present.

All 112 images on the homepage have alt attributes.

Is elespectador.com served over a valid certificate?

The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-12-08, which is 64 days from the date of this check. It covers
2 hostnames.

• elespectador.com
• www.elespectador.com

The certificate has 64 days left to run.

It covers 2 hostnames, so it was issued for this site specifically.

Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.

Which security headers does it set?

4 of 6 are set (Content Security Policy, X-Content-Type-Options, Referrer-Policy, Permissions-Policy). Absent: HSTS, X-Frame-Options.

Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.

How is DNS configured for elespectador.com?

elespectador.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.

Mail is handled by 1 exchanger.

An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.

Reverse DNS resolves to 192.0.66.91, 2a04:fa87:fffd::c000:425b, which usually names the hosting provider.

Who runs DNS and mail for elespectador.com?

DNS is operated by Cloudflare rather than self-hosted name servers.

Mail is handled by Microsoft 365.

The domain publishes AAAA records and accepts connections over IPv6.

What else is worth noting about elespectador.com?

32 of 34 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.

2 email addresses appear in the homepage markup, where address-harvesting crawlers will find them.

The server discloses software detail in x-powered-by, which tells an attacker what to target without them having to probe for it.

Can elespectador.com be spoofed in email?

DMARC is set to quarantine, so mail failing authentication is sent to spam rather than the inbox.

No CAA records are published, so any certificate authority may issue a certificate for this domain.

The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.

What else does elespectador.com publish?

An ads.txt file is published with 3977 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.

An app-ads.txt file is also published, which indicates mobile app inventory alongside the website.

What does robots.txt allow?

robots.txt is 7,681 bytes and names
32 user-agent groups.

It does not blanket-disallow general crawlers.

Sitemaps declared:

• https://www.elespectador.com/arc/outboundfeeds/sitemap-index/?outputType=xml
• https://www.elespectador.com/arc/outboundfeeds/sitemap/?outputType=xml
• https://www.elespectador.com/arc/outboundfeeds/video-index/?outputType=xml
• https://www.elespectador.com/arc/outboundfeeds/video-sitemap/?outputType=xml
• https://www.elespectador.com/arc/outboundfeeds/image-sitemap/?outputType=xml
• https://www.elespectador.com/arc/outboundfeeds/news-sitemap/?outputType=xml
• https://www.elespectador.com/arc/outboundfeeds/tags-sitemap/?outputType=xml

AI crawler policy

robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.

What structured data does the homepage publish?

• Organization
• WebSite
• SearchAction
• ImageObject
• WebPage

The homepage publishes 5 structured data types: Organization, WebSite, SearchAction, ImageObject, WebPage.

What does elespectador.com load from third parties?

The homepage pulls resources from 13 third-party hosts (cdn.piano.io, cdnjs.cloudflare.com, d2zajjwhe6xaiy.cloudfront.net, googletagmanager.com, news.google.com, open.spotify.com). Each one sees the visitor IP and user agent on every page load.

No cookies are set on first load.

The page links or refers to X/Twitter, Facebook, Instagram, YouTube.

Does elespectador.com settle on one address?

Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.

Both elespectador.com and www.elespectador.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.

How easily can elespectador.com be crawled?

A sitemap index is served at https://www.elespectador.com/arc/outboundfeeds/sitemap-index/?outputType=xml listing 94 entries.

A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.

What tracking does elespectador.com run?

1 tracking script detected: Google Tag Manager.

No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.

How does elespectador.com look when shared?

All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.

How are images, fonts and scripts handled?

112 images on the homepage, 108 of them lazy-loaded (96%).

Modern image formats are in use (12 WebP/AVIF references).

The page pulls 10 external stylesheets and 34 external scripts, with 7 carrying defer or async.

Responses carry edge cache edge headers, so content is served from a CDN rather than straight from the origin.

Is elespectador.com accessible and current?

The page uses 7 landmark elements and 298 ARIA attributes.

No skip-to-content link was found, which keyboard users rely on to bypass navigation.

Can search engines index elespectador.com?

Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.

The homepage carries 590 internal and 31 external links across 25 outside hosts.

Visible text is only 3.7% of the HTML, which indicates the page is assembled in the browser rather than served as content.

How is elespectador.com delivered?

The HTML is served with Cache-Control: max-age=300, must-revalidate.

The TLS certificate also covers 1 subdomain: www.elespectador.com.

• www.elespectador.com

Frequently asked questions

Does elespectador.com set the usual HTTP security headers?

It sets 4 of 6. The ones not present are: HSTS, X-Frame-Options.

Does elespectador.com allow AI crawlers?

robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.

What is elespectador.com built with?

The homepage exposes these fingerprints: WordPress, Google Tag Manager, X-Powered-By: WordPress VIP <https://wpvip.com>. A site behind a CDN or rendered server-side may use more than it reveals.

Where does this data come from?

Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.

Is any of this traffic or authority data?

No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.

I own elespectador.com and want this page removed.

Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.

Analysed 5 October 2026.
Analyse another domain →