Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations84 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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
BCDN & DeliveryCloudflareREVIEW
A+DNS Records2 A records, 9 ms lookupPASS
| A | 172.66.43.174, 172.66.40.82 |
| AAAA | 2606:4700:3108::ac42:2bae, 2606:4700:3108::ac42:2852 |
| CNAME | — |
| NS | alex.ns.cloudflare.com, hope.ns.cloudflare.com |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 aspmx2.googlemail.com |
| TXT | _vv6bir5nxaz4or3ew8m8slxfol0cg77 ahrefs-site-verification_f7ad4e11dfd0541c03cd8890a9fec82bc56eac4aa8554d52fc5bcd8... anthropic-domain-verification-3xngfz=nDPp4UBFFUbFyV5PKO5APGvEA detectify-verification=ac69cd9d14b6f85e1ff817494204dc05 facebook-domain-verification=2ast4p2moh1o6tqievgydo07s3ptn6 facebook-domain-verification=ykts7mafc8mxjobcn0z3zsw2so23fo google-site-verification=7ds00DvXOkEbCEvHaY7yiNogmGhswgbEHVwR1CQz5Jo google-site-verification=CQUDQaLE1szO-FqEj4Ad7-lufIc4Qem8PYpB49zXBxQ hubspot-developer-verification=ZTUwOGEyZTAtMzlhYS00ODQyLThiNGEtN2JiMmRiYjQ1YzYx openai-domain-verification=dv-njpai8XXfHEbChMjBbPykbx2 uber-domain-verification=847ee327-1f30-4b75-9c5c-21b6a8f69c81 v=MCPv1; k=ed25519; p=CSIm9SJgOqJNBBD0lAF1r0G7nFHNAu288k5oS4pxiDE= SPF v=spf1 include:_spf.google.com include:sendgrid.net include:sparkpostmail.com in... |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 392 ms totalPASS
https://tickettailor.com
41 ms · HTTP/1.1
https://www.tickettailor.com/
352 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://tickettailor.com | 301 | 41 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.tickettailor.com/ | 200 | 352 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 658 URLsPASS
User-agent: *
Allow: /
Disallow: /checkout/*
Disallow: /*?*bg_fill*
Disallow: /*?*widget*
Disallow: /*?*from_listings*
Disallow: /*?*_ga*
Disallow: /*?*ref*
Disallow: /*?*entry_link*
Disallow: /*?*modal_widget*
Disallow: /*?*disable-widget*
Disallow: /*?*direct*
Sitemap: https://www.tickettailor.com/sitemap.xml
- https://www.tickettailor.com/en-us/features/secure-event-ticketing
- https://www.tickettailor.com/features/sell-tickets-on-weebly
- https://www.tickettailor.com/blog/email-marketing-strategy-to-boost-ticket-sales
- https://www.tickettailor.com/en-us/features/sell-tickets-with-paypal
- https://www.tickettailor.com/features/sell-tickets-on-wix
A+Domain Intelligencetickettailor.com — via Cloudflare, Inc., 16 years, 1 months old, hosted on CloudflarePASS
307 days
May 21, 2027
84 days
Issued by Google Trust Services
16 years, 1 months
Registered May 21, 2010
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
172.66.43.174
Cloudflare, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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