Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1341 ms totalFIX
https://real.com
465 ms · HTTP/1.1
https://www.real.com/
713 ms · HTTP/1.1
https://www.real.com/es
163 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://real.com | 301 | 465 ms | HTTP/1.1 | Apache |
| 2 | https://www.real.com/ | 302 | 713 ms | HTTP/1.1 | Apache-Coyote/1.1 |
| 3 | https://www.real.com/es | 200 | 163 ms | HTTP/1.1 | Apache-Coyote/1.1 |
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.
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 & Recommendations245 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, 157 ms lookupPASS
| A | 75.2.98.202, 99.83.157.179 |
| AAAA | — |
| CNAME | — |
| NS | ns50.real.com, ns30.real.com, ns40.real.com, ns20.real.com |
| MX | 10 mx1-us1.ppe-hosted.com 20 mx2-us1.ppe-hosted.com |
| TXT | ppe-f0a704b1e8dbdddf5a9f google-site-verification=fOxdbFV3jtMb00RL1f5LedIqcUVlX5zohBi0KbrL85Q 3smcsmyngktvrqqpbs0tpgr1q755bw5m amazonses:XZEmKpflX9V3uk7bCKDz6aSylCvgRDQtkrqBff7ovh4= TGfp59qUqO0gIPJyUnIDGm6KUGy1FWi3xElZk42pkwdxKVLeXVSl1Fxt8Jn8qLVAM2vAAy3qyFYyq3Wm... SPF v=spf1 mx ip4:207.188.18.10/31 ip4:207.188.25.200/30 ip4:213.128.132.196/31 ip4:... |
| 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+Crawlabilityrobots.txt present, sitemap with 50 URLsPASS
# /robots.txt file for https://www.real.com
User-agent: *
Sitemap: https://www.real.com/sitemap.xml
Disallow: /dmm/
Disallow: /realplayer/partner/
Disallow: /realplayer/affiliate/
Disallow: /realplayer/action-sports/
Disallow: /realplayer/thankyou/
Disallow: /realplayer/trigger/
Disallow: /sem/
Disallow: /em/
Disallow: /affiliate/
Allow: /realplayer/download-video
Disallow: /realplayer/
Disallow: /download/
Disallow: /realtimes/trigger/
Disallow: /*/dmm/
Disallow: /*/realplayer/partner/
Disallow: /*/realplayer/affiliate/
Disallow: /*/realplayer/action-sports/
Disallow: /*/realplayer/thankyou/
Disallow: /*/realplayer/trigger/
Disallow: /*/sem/
Disallow: /*/em/
Disallow: /*/affiliate/
Disallow: /*/realplayer/
Disallow: /*/download/
Disallow: /*/realtimes/trigger/
# changes
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencereal.com — via GoDaddy.com, LLC, 29 years, 9 months old, hosted on AWSPASS
158 days
December 23, 2026
245 days
Issued by DigiCert Inc
29 years, 9 months
Registered December 24, 1996
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
75.2.98.202
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