Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.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
User-agent: *
Disallow: /wp-admin/
Disallow: /wp-admin/admin-ajax.php*
Disallow: /downloads/
Disallow: /account/
Disallow: /?s
Disallow: /search/
Disallow: */trackback
Disallow: */feed
Disallow: */rss
Disallow: */embed
Disallow: */wlwmanifest.xml
Disallow: */xmlrpc.php
Disallow: /blocksy/wp-admin/
Disallow: /blocksy/wp-admin/admin-ajax.php*
Disallow: /blocksy/downloads/
Disallow: /blocksy/account/
Disallow: /blocksy/?s
Disallow: /blocksy/search/
Disallow: /blocksy/roadmap/
Disallow: /blocksy/requests/
Disallow: /blocksy/go/
Disallow: /new-blocksy/
Sitemap: https://creativethemes.com/blocksy/sitemap_index.xml
BTLS Certificate Expiry & Recommendations78 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records3 A records, 40 ms lookupPASS
| A | 104.26.1.54, 172.67.71.54, 104.26.0.54 |
| AAAA | 2606:4700:20::681a:36, 2606:4700:20::ac43:4736, 2606:4700:20::681a:136 |
| CNAME | — |
| NS | mary.ns.cloudflare.com, huxley.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | google-site-verification=TWUwllURzK286KcK9t60hp1kiAlhkee5rhwJCs5FHIk SPF v=spf1 ip4:172.246.27.186 include:spf.sendinblue.com include:spf.mandrillapp.com... sendinblue-code:07063c7314c5c43f33fb54aad8e4b3fc google-site-verification=iQ6WASKn8aBdCAbC4qEDGWEkYUFgGF7-1SaOjUI2eKM |
| 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), 367 ms totalPASS
https://creativethemes.com
201 ms · HTTP/1.1
https://creativethemes.com/blocksy/
166 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://creativethemes.com | 302 | 201 ms | HTTP/1.1 | cloudflare |
| 2 | https://creativethemes.com/blocksy/ | 200 | 166 ms | HTTP/1.1 | cloudflare |
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 (16 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencecreativethemes.com — via GoDaddy.com, LLC, 21 years, 10 months oldPASS
66 days
September 22, 2026
78 days
Issued by Google Trust Services
21 years, 10 months
Registered September 22, 2004
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::ac43:4736
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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