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
BRedirect Chain2 redirect(s), 454 ms totalREVIEW
https://studiopress.com
74 ms · HTTP/1.1
http://www.studiopress.com/
194 ms · HTTP/1.1
https://www.studiopress.com/
186 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://studiopress.com | 301 | 74 ms | HTTP/1.1 | cloudflare |
| 2 | http://www.studiopress.com/ | 301 | 194 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.studiopress.com/ | 200 | 186 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
Redirect directly from https://studiopress.com to https://www.studiopress.com/
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: web.dev
BTLS Certificate Expiry & Recommendations47 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, 43 ms lookupPASS
| A | 104.16.144.149, 104.17.159.228 |
| AAAA | 2606:4700::6810:9095, 2606:4700::6811:9fe4 |
| CNAME | — |
| NS | rick.ns.cloudflare.com, chin.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | google-site-verification=AsvLjeYAMb6mh4_vtAb_xyoaVCSL3-ymK-Py-iJn3Rk google-site-verification=93Y9sHwBjczGCB5au-H2l9qsTi1hT2e07HXwELusBnI SPF v=spf1 mx include:_spf.google.com include:mailgun.org ip4:50.23.155.101 ip4:52.3... facebook-domain-verification=3a7j5t4rwm680e7uiqm4igcp78uvo5 |
| 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.
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 13 URLsPASS
Crawl-delay: 10
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:
Sitemap: https://www.studiopress.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
- https://www.studiopress.com/post-sitemap...
- https://www.studiopress.com/page-sitemap...
- https://www.studiopress.com/attachment-s...
- https://www.studiopress.com/sp-themes-si...
- https://www.studiopress.com/surl-sitemap...
- https://www.studiopress.com/landing-page...
- https://www.studiopress.com/category-sit...
- https://www.studiopress.com/post_tag-sit...
- https://www.studiopress.com/theme-catego...
- https://www.studiopress.com/theme-featur...
- https://www.studiopress.com/theme-layout...
- https://www.studiopress.com/theme-type-s...
- https://www.studiopress.com/author-sitem...
A+Domain Intelligencestudiopress.com — via MarkMonitor Inc., 24 years, 4 months oldPASS
667 days
April 12, 2028
47 days
Issued by Google Trust Services
24 years, 4 months
Registered April 12, 2002
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6810:9095
MarkMonitor 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