Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
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: daumoa
Disallow: /
User-agent: Sosospider
Disallow: /
User-agent: Snoopy
Disallow: /
User-agent: Browsershots
Disallow:
User-agent: *
Disallow: /download/legacy/
Disallow: /download/next/
Disallow: /download/sdk/
Disallow: /download/source/
Disallow: /download/test/
Disallow: /issues/
Disallow: /includes/
Disallow: /search/
Disallow: /servlets/
Disallow: /scripts/
Disallow: /support/test/
Disallow: /test/
Disallow: /banners/
Disallow: /xx/
Disallow: /ar/Archive/
Disallow: /bg/Archive/
Disallow: /cs/Archive/
Disallow: /da/Archive/
Disallow: /de/Archive/
Disallow: /el/Archive/
Disallow: /eo/Archive/
Disallow: /et/Archive/
Disallow: /eu/Archive/
Disallow: /fi/Archive/
Disallow: /gl/Archive/
Disallow: /hi/Archive/
Disallow: /hy/Archive/
Disallow: /lt/Archive/
Disallow: /nl/Archive/
Disallow: /om/Archive/
Disallow: /pl/Archive/
Disallow: /ro/Archive/
Disallow: /ru/Archive/
Disallow: /sr/Archive/
Disallow: /sv/Archive/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations80 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
ADNS Records1 A records, 33 ms lookupPASS
| A | 65.108.131.22 |
| AAAA | 2a01:4f9:6b:2ecf::2 |
| CNAME | — |
| NS | ns-1475.awsdns-56.org, ns-1864.awsdns-41.co.uk, ns-850.awsdns-42.net, ns-92.awsdns-11.com |
| MX | 10 mx2-lw-us.apache.org 10 mx1-lw-us.apache.org 10 mx2-lw-eu.apache.org 10 mx1-lw-eu.apache.org |
| TXT | google-site-verification=APex4UHAn89Afd8VTdpajESR02dAhAy4oq1-QSImEok |
| 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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
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)
ARedirect Chain1 redirect(s), 682 ms totalPASS
https://openoffice.org
333 ms · HTTP/1.1
https://www.openoffice.org/
349 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://openoffice.org | 302 | 333 ms | HTTP/1.1 | Apache |
| 2 | https://www.openoffice.org/ | 200 | 349 ms | HTTP/1.1 | Apache |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
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
A+IPv6 ReadinessIPv6 reachable (96 ms)PASS
A+Domain Intelligenceopenoffice.org — via NameCheap, Inc., 27 years, 3 months oldPASS
697 days
June 12, 2028
80 days
Issued by Sectigo Limited
27 years, 3 months
Registered June 12, 1999
Not enabled
Protects against DNS spoofing
Unknown
2a01:4f9:6b:2ecf::2
NameCheap, Inc.
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