Skip to content
https://wwd.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

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
A+
DNS Records
1 A records, 5 ms lookup
PASS
1 A records, 5 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.184
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1048.awsdns-03.org, ns-181.awsdns-22.com, ns-1872.awsdns-42.co.uk, ns-688.awsdns-22.net
Info::
1 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: 5 ms
Got: 5 ms
A192.0.66.184
AAAA—
CNAME—
NSns-1048.awsdns-03.org, ns-181.awsdns-22.com, ns-1872.awsdns-42.co.uk, ns-688.awsdns-22.net
MX
10 wwd-com.mail.protection.outlook.com
TXT
MS=ms51001314
adobe-idp-site-verification=5f299ac5ccddedab8418f37aad62a1ff499e5979c3b247bd4229...
atlassian-domain-verification=nprFKP7f9bTtDxCbcLk3c0Ag6DYYRzhq/pIp/XJkAvuuP9aQ2b...
facebook-domain-verification=egagqxkfdi9rkkfyx4qhdjqm4v8vj8
google-site-verification=LsTJad0F9rn-gOe9XIDBw3eiTmYxALhR_oWhE6r_kdg
google-site-verification=xn-AytqlDqAo-PO49Y7XBnfzY8P9C9AfnFLd7pzUOKg
pardot1033643=5421092b86f286e86589225b5b739659debe58965dce0953942d53d2944549e1
s0w6q1zbp77cgxsc9s668y4y40gwspqt
tollbit-domain-verification=a251c2d259bbbc40dd7b4128ab6c38ce02ff3ce5d7d7b2a0fbba...
SPF v=spf1 mx:phys.com ip4:69.2.108.1 include:dartmail.net include:_spf.salesforce.c...
CAALookup not available with standard resolver
Resolved in 5 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://wwd.com

https://wwd.com

9 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wwd.com2009 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 983 URLs
PASS
robots.txt present, sitemap with 983 URLs
Info::
robots.txt is present
Got: 1305 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 983 entries
Info::
Sitemap index with 983 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1305 B Sitemaps referenced 2 User-agents Claude-Web, Google-Extended, Timpibot, cXensebot, anthropic-ai, OAI-SearchBot, ClaudeBot, FacebookBot, Meta-ExternalAgent, Applebot-Extended, CCBot, ChatGPT, GPTBot, Diffbot, PerplexityBot, *, cohere-ai, omgilibot, Bytespider, DeepSeekBot, Meta-ExternalFetcher, Webzio-Extended, YouBot, omgili, ChatGPT-User, DeepSeek Blocking No — crawling allowed
User-agent: *
Disallow: /account/
Disallow: /wp-json/wwd/v1/login/
Sitemap: https://wwd.com/sitemap_index.xml
Sitemap: https://wwd.com/news-sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /?s=
Disallow: /*/?s=
Disallow: /search/
Disallow: /search?
Disallow: *?v02
Disallow: *?replytocom
Disallow: /*preview=true
Disallow: /*theme_preview=true

User-agent: anthropic-ai
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: omgili
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ChatGPT
Disallow: /

User-agent: DeepSeek
Disallow: /

User-agent: DeepSeekBot
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: Meta-ExternalAgent
Disallow: /

User-agent: Meta-ExternalFetcher
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: Webzio-Extended
Disallow: /

User-agent: YouBot
Disallow: /
User-agent: cXensebot
Crawl-delay: 5
sitemap.xml 200 OK
Type Sitemap Index URLs 983 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.wwd.com/
200https://wwd.com/

Preferred variant: non-www

HTTP → HTTPS

301http://wwd.com/ → https://wwd.com/

Consistent

A+
Domain Intelligence
wwd.com — via eNom, LLC, 31 years, 1 months old, hosted on WordPress.com (Automattic)
PASS
wwd.com — via eNom, LLC, 31 years, 1 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Aug 2, 2026 (3 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: eNom, LLC
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.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

47 days

August 2, 2026

SSL certificate

51 days

Issued by Let's Encrypt

Domain age

31 years, 1 months

Registered August 3, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.184

Registrar

eNom, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar eNom, LLC
Created August 3, 1995 (31 years, 1 months ago)
Expires August 2, 2026 (3 months)
Last Updated July 4, 2025
Name Servers ns-1048.awsdns-03.org, ns-181.awsdns-22.com, ns-1872.awsdns-42.co.uk, ns-688.awsdns-22.net
DNSSEC Not enabled
Hosting
IP Address 192.0.66.184
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
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 15 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 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.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
11 ms
Total Time Total request time from DNS lookup through full response.
16 ms

Connection waterfall

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

Send Feedback