Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1156 ms totalREVIEW
https://webpagetest.org
722 ms · HTTP/1.1
https://www.webpagetest.org/
434 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://webpagetest.org | 301 | 722 ms | HTTP/1.1 | redirectv2 |
| 2 | https://www.webpagetest.org/ | 200 | 434 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
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: *
Disallow: /result/
Disallow: /testlog/
Disallow: /testlog.php
Disallow: /forums/attachment.php
Disallow: /forums/member.php
Disallow: /forums/memberlist.php
Disallow: /forums/calendar.php
Disallow: /forums/misc.php
Disallow: /results/
Disallow: /apc/
Disallow: /work/
Allow: /
User-agent: Mediapartners-Google
Allow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations63 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
ADNS Records3 A records, 419 ms lookupPASS
| A | 98.83.184.133, 100.28.104.175, 54.157.108.158 |
| AAAA | 2600:1f18:297:ba18:6ddc:5d8f:6053:f003, 2600:1f18:297:ba0e:7900:f622:48a8:f266, 2600:1f18:297:ba24:b508:76de:f4a:df34 |
| CNAME | — |
| NS | dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, ns01.catchpointdns.com, ns02.catchpointdns.com, ns03.catchpointdns.com, ns04.catchpointdns.com |
| MX | 1 webpagetest-org.mail.protection.outlook.com |
| TXT | SPF v=spf1 include:spf.protection.outlook.com include:mail.zendesk.com include:55953... _globalsign-domain-verification=IG4UdrI9gc_SVSE132aTagdWhxkvONdbIBhHhhcMlP MS=ms45209245 ca3-dc465e5e8bc74befb3c533c4e5d3bc04 google-site-verification=eFw-55oB7R0G_2zC5m4sZ2lAbOGL_4SoA9K4PCvxhQs 5hldpurk85tj6stc3k8am74bli google-site-verification=AXshepslnkAzynzUmsebdpLslhBQU25Meu8_WlJCuME |
| 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.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+IPv6 ReadinessIPv6 reachable (121 ms)PASS
A+Domain Intelligencewebpagetest.org — via GoDaddy Corporate Domains, LLC, 18 years, 7 months oldPASS
1577 days
December 11, 2030
63 days
Issued by Let's Encrypt
18 years, 7 months
Registered December 11, 2007
Not enabled
Protects against DNS spoofing
Unknown
2600:1f18:297:ba18:6ddc:5d8f:6053:f003
GoDaddy Corporate Domains, 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