Skip to content
https://study.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Santa Clara, United States
403 Forbidden
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 250 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 250 B Sitemaps referenced 0 User-agents CCBot, *, AhrefsBot, SemrushBot Blocking No — crawling allowed
User-Agent: *
Disallow: /search/quicksearch.html
Disallow: /search/find.html
Disallow: /search/text/academy.html
Disallow: /support/search/
Allow: /

User-agent: AhrefsBot
Disallow: /

User-agent: SemrushBot
Disallow: /

User-agent: CCBot
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

255
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 (LambdaGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: SFO5-P1)
Got: x-amz-cf-id: 6qne6TYuNlXRIyDlQSsUe85LXgWwbdhmsiCo2dA3yFzTW74CGXY37A==
Info::
CDN cache status: LambdaGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status LambdaGeneratedResponse from cloudfront Evidence x-amz-cf-id: 6qne6TYuNlXRIyDlQSsUe85LXgWwbdhmsiCo2dA3yFzTW74CGXY37A==
A+
DNS Records
4 A records, 31 ms lookup
PASS
4 A records, 31 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 108.138.246.60, 108.138.246.7, 108.138.246.52, 108.138.246.35
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1304.awsdns-35.org, ns-1779.awsdns-30.co.uk, ns-392.awsdns-49.com, ns-624.awsdns-14.net
Info::
1 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: 31 ms
Got: 31 ms
A108.138.246.60, 108.138.246.7, 108.138.246.52, 108.138.246.35
AAAA
CNAME
NSns-1304.awsdns-35.org, ns-1779.awsdns-30.co.uk, ns-392.awsdns-49.com, ns-624.awsdns-14.net
MX
0 study-com.mail.protection.outlook.com
TXT
MS=ms53113204
anthropic-domain-verification-rpq4ch=KMgCpOdKlhyxDcpnZpOYPqvaA
apple-domain-verification=WU33XtJXYKYWBMFX
cl_verification=c82fcdfd-f3e8-440e-a553-075ccfb9af20
cursor-domain-verification-ny0f80=30Aq6N8hwrj7srchColYKffpq
duo_sso_verification=MNU9cp5aDypJt2DBAGz4CAKM7ijf4ndFkFQGV5RXGAvm7TXuFTE8NryAF4T...
facebook-domain-verification=tsae1foie2qaareu3im55ce7f94um4
google-site-verification=npT3ySvxTpGr9K-IVFznVPyvQGXizsuSqfZwZ6OM9sw
jetbrains-domain-verification=873cp9sujsg84omvia609id4y
notion-domain-verification=JVpsroUh51QRmm3c0qgf6BAlXGueQVsgk77WYIxsV4n
openai-domain-verification=dv-pWizcYPDNLxMW4Cq4ZpH5Dig
tinfoil-site-verification: 7f6e32f1d799323409819484f7f443d54ad67003=e5de9446f661...
SPF v=spf1 ip4:54.165.180.232 include:transmail.net include:spf.clearslide.com inclu...
zoho-verification=zb44730188.zmverify.zoho.com
CAALookup not available with standard resolver
Resolved in 31 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
0 redirect(s), 33 ms total
PASS
0 redirect(s), 33 ms total

https://study.com

33 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://study.com40333 msHTTP/1.1CloudFront
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.study.com/
200https://study.com/

HTTP → HTTPS

301http://study.com/ https://study.com/

Consistent

A+
Domain Intelligence
study.com — via GoDaddy.com, LLC, 31 years, 1 months old, hosted on AWS
PASS
study.com — via GoDaddy.com, LLC, 31 years, 1 months old, hosted on AWS
Info::
Domain registered until Aug 15, 2031 (5 years, 4 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: GoDaddy.com, 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

1888 days

August 15, 2031

SSL certificate

255 days

Issued by GlobalSign nv-sa

Domain age

31 years, 1 months

Registered August 16, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

108.138.246.35

Registrar

GoDaddy.com, 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 GoDaddy.com, LLC
Created August 16, 1995 (31 years, 1 months ago)
Expires August 15, 2031 (5 years, 4 months)
Last Updated July 24, 2023
Name Servers ns-1304.awsdns-35.org, ns-1779.awsdns-30.co.uk, ns-392.awsdns-49.com, ns-624.awsdns-14.net
DNSSEC Not enabled
Hosting
IP Address 108.138.246.35
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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 53 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
16 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
53 ms
Total Time Total request time from DNS lookup through full response.
54 ms

Connection waterfall

DNS Lookup 16 ms TCP Connect 3 ms TLS Handshake 7 ms Server Processing 27 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