Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations126 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
A+DNS Records3 A records, 34 ms lookupPASS
| A | 34.196.44.82, 52.22.70.156, 3.229.165.101 |
| AAAA | — |
| CNAME | — |
| NS | ns-1044.awsdns-02.org, ns-1753.awsdns-27.co.uk, ns-362.awsdns-45.com, ns-999.awsdns-60.net |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | 00d0b000000dvjneaw facebook-domain-verification=d2kqx5o5idc0czvlbypy06c721pf9v google-site-verification=DRwMRXEBYGtZLT9oxw2HnjLDkh8y_MhJADnD3LmiCM4 google-site-verification=I-TulKIDbi7MZgk9NGlBuSCKXYPmRozQNIW4sWYSQ_U google-site-verification=PuLdBbF-R8CBv-tHzii42hDiOTwDqLDLJfuwqggmUPI SPF v=spf1 include:_spf.google.com ip4:192.245.12.0/24 include:servers.mcsv.net incl... |
| 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.
A+Redirect ChainNo redirects — direct accessPASS
https://mix.com
322 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://mix.com | 200 | 322 ms | HTTP/1.1 |
A+Crawlabilityrobots.txt present, sitemap with 172 URLsPASS
# User-agent: Googlebot
# User-agent: Bingbot
# User-agent: baiduspider
# User-agent: Applebot
# User-agent: Yandex
# Microsoft Search Engine Robot
# User-agent: msnbot
# Yahoo! Search Engine Robot
# User-agent: Slurp
User-agent: AhrefsBot
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: *
Disallow: /api/
Disallow: /admin/
Disallow: /invitation
Disallow: /settings
Disallow: /update-settings
Disallow: /auth/
Disallow: /setup
Disallow: /styleguide
Disallow: /add
Disallow: /mixit
Disallow: /embed
Disallow: /bookmark$
Disallow: /extension$
Disallow: /auth-return
Disallow: /i/:q
Disallow: /mix/:q
Disallow: /interest/:q
Disallow: /search/:q
Disallow: /:username
Disallow: /invite/:username
Disallow: /share/:url_hash
Disallow: /!:url_hash
Sitemap: https://mix.com/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencemix.com — via SafeNames Ltd., 34 years, 11 months old, hosted on AWSPASS
482 days
November 12, 2027
126 days
Issued by Amazon
34 years, 11 months
Registered November 13, 1991
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
3.229.165.101
SafeNames Ltd.
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