Skip to content
https://movember.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
1 redirect(s), 1447 ms total
REVIEW
1 redirect(s), 1447 ms total
Info::
Single redirect
Got: https://movember.com → https://nl.movember.com/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://movember.com
Warning::
Redirect overhead: 1447 ms total
Got: 1447 ms
Info::
Cross-domain redirect detected

https://movember.com

266 ms · HTTP/1.1

302

https://nl.movember.com/

1181 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://movember.com302266 msHTTP/1.1
2https://nl.movember.com/2001181 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 26 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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.

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 26 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:  

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

127
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
4 A records, 12 ms lookup
PASS
4 A records, 12 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 52.85.47.10, 52.85.47.117, 52.85.47.58, 52.85.47.121
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1269.awsdns-30.org, ns-1865.awsdns-41.co.uk, ns-384.awsdns-48.com, ns-539.awsdns-03.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: 12 ms
Got: 12 ms
A52.85.47.10, 52.85.47.117, 52.85.47.58, 52.85.47.121
AAAA
CNAME
NSns-1269.awsdns-30.org, ns-1865.awsdns-41.co.uk, ns-384.awsdns-48.com, ns-539.awsdns-03.net
MX
0 movember-com.mail.protection.outlook.com
TXT
1679790cc6f0b81a7497a31eb3628bb0
SFMC-LZeI2tROKsePyGNOOa7dbvc_x70JLT1VWYhgNiZq
Validity-Domain-Verification=2TPDNiuf/c0k+Fyx+pOEWHNk/2Y=
anthropic-domain-verification-xr95j1=FmEypjb5KX6KlvRiN4G9jVj5Y
atlassian-domain-verification=iEl/2DSlX79Rv2X5KxVpNHde5y5OxhoJKNaO6NzfrXV6KjG3uU...
canva-site-verification=hlRUzTXS9hVXcypednynXQ
google-site-verification=5QpKXxb7eb7q72RjsNMHUE0I9su9cqRx-GW36nFmC_M
google-site-verification=755GEt-3dezn0FvoGBimO1emHw7pVncutaywHY4Sh1A
jamf-site-verification=QEjbvpdZ5c7hAPmfu5lSLQ
knowbe4-site-verification=689b993e6430f62160e309cac60ff7a3
lhbti7pt6q4n7bjmntre2iohir
mixpanel-domain-verify=ff713170-8a08-43e6-be09-c5bf68992906
onetrust-domain-verification=4cb2180a17994b9b8c72e6281fa39e2f
parkable-domain-verification=BerEQ5YmALzHLLOqDXz8YDjXz-JKrJ4A93GEYd6v5d0=
twilio-domain-verification=0e60c748e28be7877b51eac1055deb7d
v=DMARC1; p=reject; pct=100; rua=mailto:dmarc_agg@vali.email;
SPF v=spf1 include:spf-ip.movember.com include:spf.au.exclaimer.net include:_spf.sal...
CAALookup not available with standard resolver
Resolved in 12 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+
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

302https://www.movember.com/
200https://movember.com/

Preferred variant: non-www

HTTP → HTTPS

301http://movember.com/ https://movember.com/

Consistent

A+
Domain Intelligence
movember.com — via Netregistry Wholesale Pty Ltd, 22 years old, hosted on AWS
PASS
movember.com — via Netregistry Wholesale Pty Ltd, 22 years old, hosted on AWS
Info::
Domain registered until Jul 29, 2028 (2 years, 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: Netregistry Wholesale Pty Ltd
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: AWS
Got: AS16509
Domain expiry

777 days

July 29, 2028

SSL certificate

127 days

Issued by Amazon

Domain age

22 years

Registered July 29, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.173.161.41

Registrar

Netregistry Wholesale Pty Ltd

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 Netregistry Wholesale Pty Ltd
Created July 29, 2004 (22 years ago)
Expires July 29, 2028 (2 years, 3 months)
Last Updated May 30, 2023
Name Servers ns-1269.awsdns-30.org, ns-1865.awsdns-41.co.uk, ns-384.awsdns-48.com, ns-539.awsdns-03.net
DNSSEC Not enabled
Hosting
IP Address 3.173.161.41
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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 508 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 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.
6 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
509 ms
Total Time Total request time from DNS lookup through full response.
509 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 491 ms Content Transfer 0 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: AMS56-P1)
Got: x-amz-cf-id: UPvrvrMTMLM2bFql6Pol5XS8B_omrcWqrRVa19v1FH175OFoGSEOkg==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: UPvrvrMTMLM2bFql6Pol5XS8B_omrcWqrRVa19v1FH175OFoGSEOkg==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback