Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction3 redirect(s), 479 ms totalFIX
https://firstclasspov.com
65 ms · HTTP/1.1
https://www.firstclasspov.com/
169 ms · HTTP/1.1
https://www.firstclasspov.com/censorship...
69 ms · HTTP/1.1
https://www.firstclasspov.com/audience-p...
176 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://firstclasspov.com | 301 | 65 ms | HTTP/1.1 | Apache |
| 2 | https://www.firstclasspov.com/ | 302 | 169 ms | HTTP/1.1 | Apache |
| 3 | https://www.firstclasspov.com/censorship... | 301 | 69 ms | HTTP/1.1 | Apache |
| 4 | https://www.firstclasspov.com/audience-p... | 200 | 176 ms | HTTP/1.1 | Apache |
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
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
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/1 IPs match cert SANREVIEW
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
BTLS Certificate Expiry & Recommendations35 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
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
ADNS Records1 A records, 17 ms lookupPASS
| A | 66.254.114.173 |
| AAAA | — |
| CNAME | — |
| NS | ns0.reflected.net, ns1.reflected.net |
| MX | — |
| TXT | — |
| 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
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)
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 13ms across 3 resolvers (spread 21ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 975 URLsPASS
User-Agent: *
Disallow: /assets/
Disallow: /content/
Disallow: /css/
Disallow: /fonts/
Disallow: /img/
Disallow: /js/
Disallow: /owl/
sitemap: https://mrluckypov.com/sitemap.php
User-agent: YandexVideoParser
Disallow: /
User-agent: 008
Disallow: /
User-Agent: BLEXBot
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: Mail.Ru
Crawl-delay: 30
User-agent: Baiduspider
Crawl-delay: 30
User-agent: MSNBot
Crawl-delay: 7
User-agent: Bingbot
Crawl-delay: 5
User-agent: Slurp
Crawl-delay: 7
User-agent: Yandex
Crawl-delay: 10
User-agent: CCBot
Crawl-Delay: 30
User-agent: dotbot
Crawl-Delay: 5
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencefirstclasspov.com — via GoDaddy.com, LLC, 16 years, 7 months old, hosted on REFLECTED - Reflected Networks, Inc., USPASS
213 days
March 19, 2027
35 days
Issued by Let's Encrypt
16 years, 7 months
Registered March 19, 2010
Not enabled
Protects against DNS spoofing
REFLECTED - Reflected Networks, Inc., US
ASN AS29789
66.254.114.173
GoDaddy.com, LLC
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