Skip to content
https://web.gencat.cat

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 9 REVIEW 1 FIX
D
Redirect Chain
Action
3 redirect(s), 17 ms total
FIX
3 redirect(s), 17 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://web.gencat.cat/ca

https://web.gencat.cat

6 ms · HTTP/1.1

301

https://web.gencat.cat/ca

5 ms · HTTP/1.1

302

https://web.gencat.cat/ca/inici.html

1 ms · HTTP/1.1

301

https://web.gencat.cat/ca/inici

5 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://web.gencat.cat3016 msHTTP/1.1
2https://web.gencat.cat/ca3025 msHTTP/1.1
3https://web.gencat.cat/ca/inici.html3011 msHTTP/1.1
4https://web.gencat.cat/ca/inici2005 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

B
DNS Records
4 A records, 24 ms lookup
REVIEW
4 A records, 24 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.67.10, 151.101.195.10, 151.101.131.10, 151.101.3.10
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: cdn.adobeaemcloud.com
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 24 ms
Got: 24 ms
A151.101.67.10, 151.101.195.10, 151.101.131.10, 151.101.3.10
AAAA—
CNAMEcdn.adobeaemcloud.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 24 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 151.101.67.10: lookup 151.101.67.10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.195.10: lookup 151.101.195.10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.131.10: lookup 151.101.131.10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.3.10: lookup 151.101.3.10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
Crawlability
Action
robots.txt present, sitemap with 9 URLs
REVIEW
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 1034 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
robots.txt references sitemap

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

robots.txt 200 OK
Size 1034 B Sitemaps referenced 3 User-agents Sputnik, Algolia Crawler, Bing, Googlebot, Slurp, Baiduspider, SputnikBot/2.3, SFbot, *, Google-CloudVertexBot, ia_archiver, Twitterbot, Yandex, SputnikBot Blocking Yes — all crawlers blocked
User-agent: *
Disallow: /

#Algolia-Crawler-Verif: B80761741539486D
User-agent: Algolia Crawler
Allow: /*/sitemap-oposicions.xml
Allow: /*/generalitat/treballar-generalitat/oposicions/*
Sitemap: https://web.gencat.cat/ca/sitemap-oposicions.xml
Sitemap: https://web.gencat.cat/en/sitemap-oposicions.xml
Sitemap: https://web.gencat.cat/es/sitemap-oposicions.xml

# Allow Vertex AI Search bot to crawl specific language directories
User-agent: Google-CloudVertexBot
Allow: /ca/
Allow: /en/
Allow: /es/
Disallow: /

#Bot WayBackMachine
User-Agent: ia_archiver
Disallow:

#Bot Bing
User-agent: Bing
Disallow: /*?

#Bot Google
User-agent: Googlebot
Disallow: /*?

#Bot Yahoo
User-agent: Slurp
Disallow: /*?


#Bot Twitter
User-agent: Twitterbot
Disallow:

#Baiduspider
User-agent: Baiduspider
Disallow: /
 
#Yandex
User-agent: Yandex
Disallow: /

#SputnikBot
User-agent: SputnikBot
Disallow: /

#Sputnik
User-agent: Sputnik
Disallow: /

#SputnikBot/2.3
User-agent: SputnikBot/2.3
Disallow: /

#Bot Salesforce
User-agent: SFbot
Disallow: /*?
sitemap.xml 200 OK
Type URL Set URLs 9 entries Valid XML Yes
Sample URLs:
B
TLS Certificate Expiry & Recommendations
114 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

114
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 15ms across 3 resolvers (spread 24ms)
PASS
Mean 15ms across 3 resolvers (spread 24ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 21ms
Got: 21ms via 8.8.8.8:53
Info::
Cloudflare: 25ms
Got: 25ms via 1.1.1.1:53
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.web.gencat.cat/
200https://web.gencat.cat/

HTTP → HTTPS

301http://web.gencat.cat/ → https://web.gencat.cat/

Consistent

A+
Domain Intelligence
gencat.cat — via Entorno Digital, 20 years, 9 months old, hosted on GENCAT-AS - Centre de Telecomunicacions i Tecnologies de la Informacio de la Generalitat de Catalunya, ES
PASS
gencat.cat — via Entorno Digital, 20 years, 9 months old, hosted on GENCAT-AS - Centre de Telecomunicacions i Tecnologies de la Informacio de la Generalitat de Catalunya, ES
Info::
Domain registered until Feb 14, 2027 (6 months remaining)
Info::
Registrar: Entorno Digital
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: GENCAT-AS - Centre de Telecomunicacions i Tecnologies de la Informacio de la Generalitat de Catalunya, ES
Got: AS39551
Domain expiry

181 days

February 14, 2027

SSL certificate

114 days

Issued by Sectigo Limited

Domain age

20 years, 9 months

Registered February 14, 2006

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

GENCAT-AS - Centre de Telecomunicacions i Tecnologies de la Informacio de la Generalitat de Catalunya, ES

ASN AS39551

83.247.151.41

Registrar

Entorno Digital

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Entorno Digital
Created February 14, 2006 (20 years, 9 months ago)
Expires February 14, 2027 (6 months)
Last Updated February 11, 2026
Name Servers ns1.gencat.net, ns3.gencat.cat, ns1.gencat.cat, ns2.gencat.cat, ns2.gencat.net, ns3.gencat.net
Registrant Generalitat de Catalunya
Hosting
IP Address 83.247.151.41
ASN AS39551 (GENCAT-AS - Centre de Telecomunicacions i Tecnologies de la Informacio de la Generalitat de Catalunya, ES)
Provider GENCAT-AS - Centre de Telecomunicacions i Tecnologies de la Informacio de la Generalitat de Catalunya, ES
Data source: whois (1.0s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 51 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
51 ms
Total Time Total request time from DNS lookup through full response.
51 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 1 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350077-TOJ
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-toj-leto2350077-TOJ
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 3 header(s)
Got: age=149, x-cache=HIT, x-served-by=cache-toj-leto2350077-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback