Skip to content
https://mxtoolbox.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 REVIEW
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
TLS Certificate Expiry & Recommendations
190 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

190
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
A+
DNS Records
4 A records, 55 ms lookup
PASS
4 A records, 55 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 3.164.163.88, 3.164.163.85, 3.164.163.49, 3.164.163.24
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-495.awsdns-61.com, ns-1320.awsdns-37.org, ns-1736.awsdns-25.co.uk, ns-984.awsdns-59.net
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: 55 ms
Got: 55 ms
A3.164.163.88, 3.164.163.85, 3.164.163.49, 3.164.163.24
AAAA
CNAME
NSns-495.awsdns-61.com, ns-1320.awsdns-37.org, ns-1736.awsdns-25.co.uk, ns-984.awsdns-59.net
MX
0 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
SPF v=spf1 redirect=mxtoolbox.com.hosted.spf-report.com
google-site-verification=a72lcHiaH48r427O4d4O6SrvOBQkmH4IGZ98mH9YWwU
yahoo-verification-key=VtY1K1/IZ0c2E6oFnpXiTymAITi3lqo8IlXNDII0LdE=
6ffyqp6bfm0xx4bcgd1ybz0jtknhgpdy
lml8nrmxdc063ms0skf3bnvm2zvslffz
mailru-verification: 18440d267f8068a2
CAALookup not available with standard resolver
Resolved in 55 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://mxtoolbox.com

https://mxtoolbox.com

152 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mxtoolbox.com200152 msHTTP/1.1Microsoft-IIS/10.0
A+
Crawlability
robots.txt present, sitemap with 39 URLs
PASS
robots.txt present, sitemap with 39 URLs
Info::
robots.txt is present
Got: 892 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 39 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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 892 B Sitemaps referenced 0 User-agents *, AhrefsBot, dotbot, meta-externalagent Blocking No — crawling allowed
# General rules for all crawlers
User-agent: *
# Block access to API endpoints
Disallow: /api/v*
# Block access to premium or user-specific content
Disallow: /pro/
# Block access to email template resources
Disallow: /public/emailtemplates/
# Block direct access to the email header analysis tool
Disallow: /public/tools/emailheaders.aspx
# Block access to unsubscribe page to avoid unnecessary indexing
Disallow: /public/unsubscribe.aspx
# Block access to checkout pages to avoid indexing dynamic purchase flows
Disallow: /public/checkout/

# Block AhrefsBot from crawling problem diagnostic tools
User-agent: AhrefsBot
Disallow: /problem/

# Block dotbot (used by Dotcom-Monitor) from domain-specific health tools
User-agent: dotbot
Disallow: /domain/
Disallow: /emailhealth/

# Block Meta AI training bots from crawling any content
User-agent: meta-externalagent
Disallow: /SuperTool.aspx

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

301https://www.mxtoolbox.com/
200https://mxtoolbox.com/

Preferred variant: non-www

HTTP → HTTPS

301http://mxtoolbox.com/ https://mxtoolbox.com/

Consistent

A+
Domain Intelligence
mxtoolbox.com — via Network Solutions, LLC, 21 years, 10 months old, hosted on AWS
PASS
mxtoolbox.com — via Network Solutions, LLC, 21 years, 10 months old, hosted on AWS
Info::
Domain registered until Sep 28, 2026 (5 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: Network Solutions, LLC
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

78 days

September 28, 2026

SSL certificate

190 days

Issued by Amazon

Domain age

21 years, 10 months

Registered September 28, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.164.163.49

Registrar

Network Solutions, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created September 28, 2004 (21 years, 10 months ago)
Expires September 28, 2026 (5 months)
Last Updated August 13, 2022
Name Servers ns-1320.awsdns-37.org, ns-1736.awsdns-25.co.uk, ns-495.awsdns-61.com, ns-984.awsdns-59.net
DNSSEC Not enabled
Hosting
IP Address 3.164.163.49
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 464 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
48 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
18 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
382 ms
Total Time Total request time from DNS lookup through full response.
465 ms

Connection waterfall

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

Send Feedback