Infrastructure - https://wufoo.com BeaverCheck Audit

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.wufoo.com/

200https://wufoo.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B

TLS Certificate Expiry & Recommendations

142 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

142

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

AWS CloudFront (LambdaGeneratedResponse from cloudfront)

REVIEW

AWS CloudFront (LambdaGeneratedResponse from cloudfront)

Site is served via AWS CloudFront CDN (edge: MAD53-P1)

Got: x-amz-cf-id: 36NmL4oIpcnDQpny729bnjIA-ZO7ZdZ0nrdTGRQLQ4HJYWWsuAoj7g==

CDN cache status: LambdaGeneratedResponse from cloudfront

CDN Detected: AWS CloudFront

Provider AWS CloudFront Cache Status LambdaGeneratedResponse from cloudfront Evidence x-amz-cf-id: 36NmL4oIpcnDQpny729bnjIA-ZO7ZdZ0nrdTGRQLQ4HJYWWsuAoj7g==

A+

DNS Records

4 A records, 28 ms lookup

PASS

4 A records, 28 ms lookup

Resolves to 4 IPv4 address(es)

Got: 18.154.29.68, 18.154.29.6, 18.154.29.121, 18.154.29.38

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-136.awsdns-17.com, ns-1104.awsdns-10.org, ns-927.awsdns-51.net, ns-1612.awsdns-09.co.uk

2 mail exchanger(s) configured

CAA records not checked

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

SPF record present in TXT

DNS resolution time: 28 ms

Got: 28 ms

A	18.154.29.68, 18.154.29.6, 18.154.29.121, 18.154.29.38
AAAA	—
CNAME	—
NS	ns-136.awsdns-17.com, ns-1104.awsdns-10.org, ns-927.awsdns-51.net, ns-1612.awsdns-09.co.uk
MX	10 us-smtp-inbound-2.mimecast.com 10 us-smtp-inbound-1.mimecast.com
TXT	facebook-domain-verification=or17saasy1m354p5mk4hxe841a68gn 0z67zpyk7zwwyqgfnjzy08whqdgm34vm 0ed1fe018aac4542176e184fcf847c5fe9780bef50 globalsign-domain-verification=jvMLQ8xH8X38HutWDQXyDJP7T-iqxBoYAg1AYT0omb MS=ms32172748 google-site-verification=0I99D7Z3RGhiV7VVMu8RoP7lyVONiKF855WPEv-0Xck bdg8bkjh5cbj6g3y0py00kwynr0ns7xp SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
CAA	Lookup not available with standard resolver

Resolved in 28 ms

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), 251 ms total

PASS

1 redirect(s), 251 ms total

Single redirect

Got: https://wufoo.com → https://www.wufoo.com/ (301)

WWW normalization redirect

https://wufoo.com

44 ms · HTTP/1.1

301

https://www.wufoo.com/

207 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://wufoo.com	301	44 ms	HTTP/1.1	CloudFront
2	https://www.wufoo.com/	200	207 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

A+

Crawlability

robots.txt present, sitemap with 18 URLs

PASS

robots.txt present, sitemap with 18 URLs

robots.txt is present

Got: 67 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 18 entries

Sitemap index with 18 child sitemaps

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 67 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

sitemap.xml 200 OK

Type Sitemap Index URLs 18 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

wufoo.com — via MarkMonitor Inc., 20 years, 6 months old, hosted on AWS

PASS

wufoo.com — via MarkMonitor Inc., 20 years, 6 months old, hosted on AWS

Domain registered until Jan 16, 2028 (1 years, 9 months remaining)

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.

Registrar: MarkMonitor Inc.

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.

Hosting: AWS

Got: AS16509

Domain expiry

579 days

January 16, 2028

SSL certificate

142 days

Issued by Amazon

Domain age

20 years, 6 months

Registered January 16, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.154.29.38

Registrar

MarkMonitor Inc.

Unlocked 4 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 MarkMonitor Inc.

Created January 16, 2006 (20 years, 6 months ago)

Expires January 16, 2028 (1 years, 9 months)

Last Updated December 15, 2025

Name Servers ns-1104.awsdns-10.org, ns-136.awsdns-17.com, ns-1612.awsdns-09.co.uk, ns-927.awsdns-51.net

DNSSEC Not enabled

Hosting

IP Address 18.154.29.38

ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (0.3s)

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 82 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

41 ms

TCP Connect

1 ms

TLS Handshake

3 ms

Time to First Byte

82 ms

Total Time

83 ms

Connection waterfall

DNS Lookup 41 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 37 ms Content Transfer 0 ms