Skip to content
https://acuityscheduling.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 4 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

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.acuityscheduling.com/
200https://acuityscheduling.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://acuityscheduling.com/ → https://acuityscheduling.com/

Use 301 (permanent) instead of 302 (temporary)

B
HTTP Probe Timing
Total 964 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
175 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
351 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
964 ms
Total Time Total request time from DNS lookup through full response.
965 ms

Connection waterfall

DNS Lookup 27 ms TCP Connect 175 ms TLS Handshake 351 ms Server Processing 411 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
178 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Add includeSubDomains to the HSTS directive
  • 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
2 A records, 27 ms lookup
PASS
2 A records, 27 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 44.252.231.134, 44.237.13.138
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-61.awsdns-07.com, ns-1765.awsdns-28.co.uk, ns-672.awsdns-20.net, ns-1079.awsdns-06.org
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: 27 ms
Got: 27 ms
A44.252.231.134, 44.237.13.138
AAAA—
CNAME—
NSns-61.awsdns-07.com, ns-1765.awsdns-28.co.uk, ns-672.awsdns-20.net, ns-1079.awsdns-06.org
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
_globalsign-domain-verification=O60kZMoa5mBPIKKqd9FSRXcGUhU6s3rzZHzWNLAlL7
google-site-verification=YmwxE0k6d4aiRozNGgPRQ21btq9TeUVXIcqjErF1nAw
facebook-domain-verification=rudfdg34yr7x51f3vi1rnv1uya5xv8
zoom-domain-verification=e5e24a65-63ae-4461-a6ce-3713aa75b88d
status-page-domain-verification=3fscwgnr7w6q
_globalsign-domain-verification=p1fktqCHnOA1sE262wg61RlM1M1TddxeBhTTQfKOf-
ps-cd-verification=c326b747-cc18-4c14-b31b-7c801c226d78
SPF v=spf1 a mx ip4:208.43.166.0/28 ip4:208.97.132.0/24 ip4:208.43.167.208/29 includ...
google-site-verification=eTUeyDSl_3VezD70iFrLfmD4Sr551_vy50KfsgLvR-Y
CAALookup not available with standard resolver
Resolved in 27 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://acuityscheduling.com

https://acuityscheduling.com

930 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://acuityscheduling.com200930 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 238 URLs
PASS
robots.txt present, sitemap with 238 URLs
Info::
robots.txt is present
Got: 941 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 238 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 941 B Sitemaps referenced 6 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /schedule.php?*action=appt*
Disallow: /schedule.php?email=*
Disallow: /schedule.php?phone=*
Disallow: /schedule.php?firstName=*
Disallow: /schedule.php?lastName=*
Disallow: /schedule.php?*&email=*
Disallow: /schedule.php?*&phone=*
Disallow: /schedule.php?*&firstName=*
Disallow: /schedule.php?*&lastName=*
Disallow: /home.php
Disallow: /appointments.php
Disallow: /new-frontsite.php
Disallow: /reports.php
Disallow: /squarespace.php
Disallow: /schedule.php?owner=12607430*
Disallow: /api/*
Disallow: /*PHPSESSID
Disallow: /unsubscribe.php
Disallow: /email-unsubscribe/*
Disallow: /*/invoice/*/pay
Sitemap: https://acuityscheduling.com/sitemap.xml
Sitemap: https://de.acuityscheduling.com/sitemap.xml
Sitemap: https://it.acuityscheduling.com/sitemap.xml
Sitemap: https://fr-fr.acuityscheduling.com/sitemap.xml
Sitemap: https://pt-br.acuityscheduling.com/sitemap.xml
Sitemap: https://es.acuityscheduling.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 238 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
acuityscheduling.com — via MarkMonitor Inc., 19 years, 6 months old, hosted on AWS
PASS
acuityscheduling.com — via MarkMonitor Inc., 19 years, 6 months old, hosted on AWS
Info::
Domain registered until Jan 15, 2028 (1 years, 9 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: MarkMonitor 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

578 days

January 15, 2028

SSL certificate

178 days

Issued by Amazon

Domain age

19 years, 6 months

Registered January 15, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

44.237.13.138

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 15, 2007 (19 years, 6 months ago)
Expires January 15, 2028 (1 years, 9 months)
Last Updated December 14, 2025
Name Servers ns-1079.awsdns-06.org, ns-1765.awsdns-28.co.uk, ns-61.awsdns-07.com, ns-672.awsdns-20.net
DNSSEC Not enabled
Hosting
IP Address 44.237.13.138
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback