Skip to content
https://reason.com

Infrastructure

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

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

Certificate validity

115
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
  • 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
1 A records, 24 ms lookup
PASS
1 A records, 24 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 75.2.24.81
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-cloud-c2.googledomains.com, ns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com
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: 24 ms
Got: 24 ms
A75.2.24.81
AAAA—
CNAME—
NSns-cloud-c2.googledomains.com, ns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com
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
google-site-verification=-AmMiilAN-pnjWt369CUWae-VQ-b9wmH4fSGyhbkQxw
google-site-verification=K5JPnpC8walfIH_ZhergSkJyTumxCo4N1CqtRxRUGz0
google-site-verification=nXIDy5Orar1umiJ8BNNv0AjfLjUNviAfbkvs7BqNg1k
tollbit-domain-verification=95a470c1deaf365ccffed5f43ddcae29683f3beb27812e8631e5...
SPF v=spf1 include:_spf.google.com include:spf.maropost.com include:servers.mcsv.net...
CAALookup not available with standard resolver
Resolved in 24 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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://reason.com

https://reason.com

620 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://reason.com200620 msHTTP/1.1nginx/1.12.2
A+
Crawlability
robots.txt present, sitemap with 224 URLs
PASS
robots.txt present, sitemap with 224 URLs
Info::
robots.txt is present
Got: 204 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 224 entries
Info::
Sitemap index with 224 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 204 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

# ---------------------------
# END YOAST BLOCK
Sitemap: https://reason.com/sitemap.xml
Sitemap: https://reason.com/sitemap.html
sitemap.xml 200 OK
Type Sitemap Index URLs 224 entries Valid XML Yes
Child Sitemaps:
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.reason.com/
200https://reason.com/

Preferred variant: non-www

HTTP → HTTPS

301http://reason.com/ → https://reason.com/

Consistent

A+
Domain Intelligence
reason.com — via Network Solutions, LLC, 29 years old, hosted on AWS
PASS
reason.com — via Network Solutions, LLC, 29 years old, hosted on AWS
Info::
Domain registered until Aug 21, 2034 (8 years, 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

2988 days

August 21, 2034

SSL certificate

115 days

Issued by Amazon

Domain age

29 years

Registered August 22, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.24.81

Registrar

Network Solutions, 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 Network Solutions, LLC
Created August 22, 1997 (29 years ago)
Expires August 21, 2034 (8 years, 5 months)
Last Updated August 21, 2024
Name Servers ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 75.2.24.81
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 654 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 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.
461 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
653 ms
Total Time Total request time from DNS lookup through full response.
655 ms

Connection waterfall

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

Send Feedback