Skip to content
https://unixtools.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 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
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.unixtools.org/
200https://unixtools.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://unixtools.org/ https://unixtools.org/

Consistent

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

Certificate validity

228
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
B
CDN & Delivery
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD56-P3)
Got: x-amz-cf-id: s9g94Qle2kAI0OTy4wRapD9b-6AI8aWTGFaNh_uo7hsXjwjcwu8saw==
Info::
CDN cache status: FunctionGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status FunctionGeneratedResponse from cloudfront Evidence x-amz-cf-id: s9g94Qle2kAI0OTy4wRapD9b-6AI8aWTGFaNh_uo7hsXjwjcwu8saw==
A+
DNS Records
4 A records, 34 ms lookup
PASS
4 A records, 34 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.154.48.112, 18.154.48.116, 18.154.48.87, 18.154.48.102
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1789.awsdns-31.co.uk, ns-552.awsdns-05.net, ns-1431.awsdns-50.org, ns-361.awsdns-45.com
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 34 ms
Got: 34 ms
A18.154.48.112, 18.154.48.116, 18.154.48.87, 18.154.48.102
AAAA
CNAME
NSns-1789.awsdns-31.co.uk, ns-552.awsdns-05.net, ns-1431.awsdns-50.org, ns-361.awsdns-45.com
MX
TXT
CAALookup not available with standard resolver
Resolved in 34 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 93 ms total
PASS
1 redirect(s), 93 ms total
Info::
Single redirect
Got: https://unixtools.org → https://www.unixtools.org/ (301)
Info::
WWW normalization redirect

https://unixtools.org

13 ms · HTTP/1.1

301

https://www.unixtools.org/

80 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unixtools.org30113 msHTTP/1.1CloudFront
2https://www.unixtools.org/20080 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 49 URLs
PASS
robots.txt present, sitemap with 49 URLs
Info::
robots.txt is present
Got: 86 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 49 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 86 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow:
Disallow: /error.html

Sitemap: https://unixtools.org/sitemap.xml
A+
Domain Intelligence
unixtools.org — via DreamHost, LLC, 27 years, 7 months old, hosted on AWS
PASS
unixtools.org — via DreamHost, LLC, 27 years, 7 months old, hosted on AWS
Info::
Domain registered until Feb 8, 2027 (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: DreamHost, 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

206 days

February 8, 2027

SSL certificate

228 days

Issued by Amazon

Domain age

27 years, 7 months

Registered February 8, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.154.48.116

Registrar

DreamHost, LLC

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 DreamHost, LLC
Created February 8, 1999 (27 years, 7 months ago)
Expires February 8, 2027 (9 months)
Last Updated February 9, 2026
Name Servers ns-1431.awsdns-50.org, ns-1789.awsdns-31.co.uk, ns-361.awsdns-45.com, ns-552.awsdns-05.net
DNSSEC Not enabled
Hosting
IP Address 18.154.48.116
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.8s)

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 50 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
41 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.
51 ms
Total Time Total request time from DNS lookup through full response.
51 ms

Connection waterfall

DNS Lookup 41 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 3 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback