diario.com — domain analysis
diario.com describes itself as "Noticias y última hora de Donostia-San Sebastián, Gipuzkoa y todas sus comarcas y municipios en El Diario Vasco". It is built on WordPress, registered in 1996, served from Kansas City, United States. It has a valid HTTPS certificate, 2 of 6 common security headers.
What is diario.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:
- para ×35
- sebasti ×25
- tras ×15
- fotos ×12
- este ×11
- madrid ×11
- gipuzkoa ×10
- desde ×10
- oferta ×10
- nbsp ×10
Does diario.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 diario.com compare with other domains analysed here?
Measured against the 13 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.
| Response time | Faster than 69% of them (median 601ms) |
|---|---|
| Security headers | More than 73% of them |
| Domain age | Older than 69% of them |
Related domains in this index
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
When was diario.com registered?
diario.com was registered on 17 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 Interdominios, Inc..
Registration runs until 18 February 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 17 February 1996 |
|---|---|
| Expires | 18 February 2027 |
| Registrar | Interdominios, Inc. |
| Registry status | client transfer prohibited |
Where is diario.com hosted?
The first address resolves to infrastructure in Kansas City, United States.
The network is operated by Google Cloud (AS396982 Google LLC).
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 diario.com running on?
diario.com exposes 1 identifiable technology: WordPress.
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.
- WordPress
How does the homepage respond?
The server answered with HTTP 200 over
HTTP.
At 149ms to first byte this response is fast for a homepage measured from a single European location.
The HTML weighs 479KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | not disclosed |
|---|---|
| Compression | gzip |
| Page size | 490,403 bytes |
| Declared language | es |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 64 characters, inside the range that displays without truncation.
A meta description of 111 characters is present.
All 147 images on the homepage have alt attributes.
| Title | El Diario Vasco – Noticias de Donostia, San Sebastián y Gipuzkoa (64 chars) |
|---|---|
| Meta description | Noticias y última hora de Donostia-San Sebastián, Gipuzkoa y todas sus comarcas y municipios en El Diario Vasco (111 chars) |
| H1 | — none — (1 on the page) |
| Canonical | https://www.diariovasco.com/ |
| Open Graph title | El Diario Vasco – Noticias de Donostia, San Sebastián y Gipuzkoa |
| Headings / images | 143 H2s, 147 images (0 without alt text) |
Is diario.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-11-22, which is 48 days from the date of this check. It covers
2 hostnames.
- vocento.com
- *.vocento.com
The certificate has 48 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
2 of 6 are set (HSTS, X-Frame-Options). Absent: Content Security Policy, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31557600 |
| Content Security Policy | no | — |
| X-Content-Type-Options | no | — |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for diario.com?
| IP addresses | 34.36.177.171 |
|---|---|
| Reverse DNS | 171.177.36.34.bc.googleusercontent.com |
| Name servers | ns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com |
| Mail (MX) | mx1.veriomail.com (pri 10), backupmx2.veriomail.com (pri 20), mx2.veriomail.com (pri 10), backupmx1.veriomail.com (pri 20) |
| SPF | not published |
| TXT records | 0 |
diario.com resolves to a single address, so there is no DNS-level redundancy.
Mail is handled by 4 exchangers.
No SPF record is published. Receiving servers therefore have no published rule for who may send mail as this domain, which makes spoofing it materially easier.
Reverse DNS resolves to 171.177.36.34.bc.googleusercontent.com, which usually names the hosting provider.
Who runs DNS and mail for diario.com?
DNS is operated by Google Cloud DNS rather than self-hosted name servers.
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about diario.com?
3 of 3 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.
24 email addresses appear in the homepage markup, where address-harvesting crawlers will find them.
Can diario.com be spoofed in email?
No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.
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 does robots.txt allow?
No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
- NewsMediaOrganization
- ImageObject
- PostalAddress
- ContactPoint
- Organization
- SiteNavigationElement
- ItemList
- ListItem
The homepage publishes 8 structured data types: NewsMediaOrganization, ImageObject, PostalAddress, ContactPoint, Organization, SiteNavigationElement, ItemList, ListItem.
What does diario.com load from third parties?
The homepage pulls resources from 13 third-party hosts (diariovasco.com, fundingchoicesmessages.google.com, oferplan.diariovasco.com, resizer.diariovasco.com, s1.ppllstatics.com, s2.ppllstatics.com). Each one sees the visitor IP and user agent on every page load.
1 cookie is set before any interaction (geo). 1 lacks the Secure flag.
1 resource is referenced over plain HTTP on an HTTPS page, which browsers block or flag as mixed content.
The page links or refers to X/Twitter, LinkedIn, Facebook, Instagram, GitHub.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| geo | no | no | none/unset |
Does diario.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
The www hostname does not respond at all, so anyone typing www.diario.com reaches nothing.
How easily can diario.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
What tracking does diario.com run?
No analytics or advertising trackers were detected on the homepage of diario.com, which is unusual for a commercial site.
How does diario.com look when shared?
4 of 5 social preview tags are set. Missing: twitter:card.
How are images, fonts and scripts handled?
147 images on the homepage, 141 of them lazy-loaded (96%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
The page pulls 1 external stylesheet and 10 external scripts, with 3 carrying defer or async.
Responses carry edge cache edge headers, so content is served from a CDN rather than straight from the origin.
Is diario.com accessible and current?
The page uses 5 landmark elements and 149 ARIA attributes.
There are 1 form inputs but only 0 label elements, so some fields may be unlabelled for screen readers.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index diario.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The canonical points to a different host (https://www.diariovasco.com/), which tells search engines the authoritative copy lives elsewhere.
The homepage carries 241 internal and 392 external links across 54 outside hosts.
Visible text makes up 6.2% of the HTML.
How is diario.com delivered?
The HTML is served with Cache-Control: max-age=0, no-cache, no-store.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
Frequently asked questions
Does diario.com set the usual HTTP security headers?
It sets 2 of 6. The ones not present are: Content Security Policy, X-Content-Type-Options, Referrer-Policy, Permissions-Policy.
Does diario.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
What is diario.com built with?
The homepage exposes these fingerprints: WordPress. 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 4 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 diario.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 4 October 2026.
Analyse another domain →
The weekly edition
Three or four things explained, in plain language, with the sources. One email a week. No spam, no algorithm in between.
