Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!DOCTYPE html>
<html>
<head>
<title>Establishing a secure connection ...</title>
<meta name="viewport" content="width=device-width, initial-scale=0.8">
<link href="https://fonts.bunny.net/css?family=Inter:300,400,500,700" rel="stylesheet">
<link href="/.bunny-shield/assets/challenge-styles.css" rel="stylesheet" />
<script src="/.bunny-shield/assets/shield-challenge.js"></script>
</head>
<body data-pow="5f6bc1a223031475dcb581b877634beefdb0311b11d70a0f7cff7e91fe76c9c9#309b8dea9cfcc301a437e3fda79c3e52#1776898794#de87fa49d2301f22e22a904834189ea581ad71e78d098aee86b009add22d3b2c">
<div class="body">
<div class="container">
<div class="left">
<img src="/.bunny-shield/assets/challenge.svg" alt="Challenge Loading" />
</div>
<div class="right">
<h1>Hold tight</h1>
<h2>
<div class="loading"></div>
We are establishing a secure
connection.
</h2>
<p>
This website is using a security service to protect
itself from online attacks. We are checking your browser
to establish a secure connection and keep you safe.
</p>
<p>
<div class="status">...</div>
<div class="error"></div>
<noscript>
<p style="color: #FF0000;">Please enable JavaScript to continue.</p>
</noscript>
</p>
</div>
</div>
</div>
<div class="footer">
Request ID: <strong>66bee6923a0e69044b0e935568e751ec</strong>
</div>
</body>
</html>
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations69 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records2 A records, 107 ms lookupPASS
| A | 193.137.200.165, 193.137.200.172 |
| AAAA | — |
| CNAME | — |
| NS | ns-2.uc.pt, ns-1.uc.pt, ns-5.uc.pt, ns02.fccn.pt |
| MX | 10 smtp.uc.pt |
| TXT | SPF v=spf1 mx ip4:193.137.200.0/25 ip4:193.137.200.156 ip4:193.137.200.144 include:s... google-site-verification=qurHCpw6Vh6M2Aczua6ByDJMkzMsbnbbibxSO46rf04 uc.pt MS=ms59602945 HARICA-vHxVPrpCoSf0xRDHcGT uc.pt MS=ms92477265 google-site-verification=yp4C2Baj3VmOlZwu-3fuV3KD6EQzEBVKKeXi-E2KMrU |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 217 ms totalPASS
https://uc.pt
52 ms · HTTP/1.1
https://www.uc.pt/
165 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://uc.pt | 301 | 52 ms | HTTP/1.1 | nginx |
| 2 | https://www.uc.pt/ | 200 | 165 ms | HTTP/1.1 | BunnyCDN-FR1-1073 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligenceuc.pt — hosted on RCCN Fundacao para a Ciencia e a Tecnologia, I.P., PTPASS
Unknown
69 days
Issued by Hellenic Academic and Research Institutions CA
Unknown
Status unknown
Protects against DNS spoofing
RCCN Fundacao para a Ciencia e a Tecnologia, I.P., PT
ASN AS1930
193.137.200.165
Registrar unknown
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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