Skip to content
https://wunderground.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.wunderground.com/
200https://wunderground.com/

HTTP → HTTPS

403http://wunderground.com/

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
259 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

259
days left
0d 30d 60d 90d+

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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 29 ms lookup
PASS
1 A records, 29 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.37.163.58
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:1380:28a::2e03, 2a02:26f0:1380:289::2e03
Info::
6 nameserver(s) configured
Got: a24-65.akam.net, a14-64.akam.net, a1-70.akam.net, a10-65.akam.net, a13-67.akam.net, a11-66.akam.net
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 29 ms
Got: 29 ms
A23.37.163.58
AAAA2a02:26f0:1380:28a::2e03, 2a02:26f0:1380:289::2e03
CNAME—
NSa24-65.akam.net, a14-64.akam.net, a1-70.akam.net, a10-65.akam.net, a13-67.akam.net, a11-66.akam.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
718768yn58v07fqwn4lhs7pqvm5zj1l4
_ob7k7pwtnbzisdnezsn1jc5ak514wuc
SPF v=spf1 mx a:zgateway.zuora.com include:spf.mandrillapp.com include:amazonses.com...
hvntc1c3swgf9n72hympkt76bjj9dj1f
google-site-verification=Fh5kgKGTJ29NEVP1BckkJXg1haNCTnTlV8_i6vgHn2s
google-site-verification=yQzqWpg6c5ULH17FBBbAZQBSAmhU9HmmMUg4B59Pxdk
amazonses:ZEJk15GPZioYapGJaTfhLf1QsErP/IxddaxpQC3eSTU=
CAALookup not available with standard resolver
Resolved in 29 ms

Multiple A records provide failover if one server goes down.

Why this matters

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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 110 ms total
PASS
1 redirect(s), 110 ms total
Info::
Single redirect
Got: https://wunderground.com → https://www.wunderground.com/ (301)
Info::
WWW normalization redirect

https://wunderground.com

11 ms · HTTP/1.1

301

https://www.wunderground.com/

99 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wunderground.com30111 msHTTP/1.1AkamaiGHost
2https://www.wunderground.com/20099 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:1380:28a::2e03, 2a02:26f0:1380:289::2e03
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:1380:28a::2e03, 2a02:26f0:1380:289::2e03 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 1272 URLs
PASS
robots.txt present, sitemap with 1272 URLs
Info::
robots.txt is present
Got: 395 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1272 entries
Info::
Sitemap index with 1272 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 395 B Sitemaps referenced 1 User-agents AmazonAdBot, * Blocking No — crawling allowed
#
# /robots.txt
#

#
# Last updated by VShrivastava 02/18/2020
#

# Disallowed for PhantomJS


# Explicit Allows

User-agent: AmazonAdBot
Allow: /

User-agent: *
# Crawl-delay: 10

# App paths
Disallow: /bundle-next/
# Directories

# Files
Disallow: /CHANGELOG.txt

# Paths (clean URLs)
# Disallow: /migration/

# Paths (no clean URLs)

Sitemap: https://www.wunderground.com/sitemaps/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1272 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
wunderground.com — via CSC Corporate Domains, Inc., 31 years, 6 months old
PASS
wunderground.com — via CSC Corporate Domains, Inc., 31 years, 6 months old
Info::
Domain registered until Mar 31, 2027 (11 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
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.
Domain expiry

288 days

March 31, 2027

SSL certificate

259 days

Issued by DigiCert Inc

Domain age

31 years, 6 months

Registered March 30, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:1380:289::2e03

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created March 30, 1995 (31 years, 6 months ago)
Expires March 31, 2027 (11 months)
Last Updated March 27, 2026
Name Servers a1-70.akam.net, a10-65.akam.net, a11-66.akam.net, a13-67.akam.net, a14-64.akam.net, a24-65.akam.net
DNSSEC Not enabled
Hosting
IP Address 2a02:26f0:1380:289::2e03
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 44 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
44 ms
Total Time Total request time from DNS lookup through full response.
44 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 8 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback