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.
BTLS Certificate Expiry & Recommendations52 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 Records1 A records, 41 ms lookupPASS
| A | 85.10.195.17 |
| AAAA | 2a01:4f8:a0:3068::2 |
| CNAME | — |
| NS | ns2.inwx.de, ns3.inwx.eu, ns.inwx.de |
| MX | 10 mx.nextcloud.com |
| TXT | SPF v=spf1 mx include:sendgrid.net include:amazonses.com include:_spf.eu.sparkpostma... google-site-verification=BRRA-GQB6KD9WDj8KhccsNho8-E0Feba52m32uuDZ5w apple-domain-verification=dTWDbt2uCnxS9nIG MS=2FF4FDA4B4C49AE44213D37A308105AA0D4EBF39 |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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.
A+Redirect ChainNo redirects — direct accessPASS
https://nextcloud.com
97 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nextcloud.com | 200 | 97 ms | HTTP/1.1 | Apache |
A+IPv6 ReadinessIPv6 reachable (28 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 11 URLsPASS
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
User-agent: *
# This section blocks all PDF files in the /media folder from being indexed
Disallow: /*.pdf$
Disallow: /media/*.pdf
- https://nextcloud.com/post-sitemap.xml
- https://nextcloud.com/post-sitemap2.xml
- https://nextcloud.com/page-sitemap.xml
- https://nextcloud.com/case_studies-sitem...
- https://nextcloud.com/whitepapers-sitema...
- https://nextcloud.com/data_sheets-sitema...
- https://nextcloud.com/press_releases-sit...
- https://nextcloud.com/event-sitemap.xml
- https://nextcloud.com/on-demand-webinar-...
- https://nextcloud.com/podcast-sitemap.xm...
- https://nextcloud.com/category-sitemap.x...
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligencenextcloud.com — via INWX GmbH, 21 years, 5 months oldPASS
251 days
February 22, 2027
52 days
Issued by Let's Encrypt
21 years, 5 months
Registered February 22, 2005
Not enabled
Protects against DNS spoofing
Unknown
2a01:4f8:a0:3068::2
INWX GmbH
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
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