Skip to content
https://www.grammarly.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
2
PASS
7
INFO
0
Probed from Santa Clara, United Stated
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
136 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

136
days left
0d 30d 60d 90d+

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 34 ms lookup
PASS
4 A records, 34 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 108.139.10.9, 108.139.10.86, 108.139.10.129, 108.139.10.76
Info::
No IPv6 (AAAA) records
Info::
No NS records found
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
A108.139.10.9, 108.139.10.86, 108.139.10.129, 108.139.10.76
AAAA
CNAME
NS
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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.grammarly.com

https://www.grammarly.com

226 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.grammarly.com200226 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 265 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 265 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /voucher/
Disallow: /social/
Disallow: /api/
Disallow: /enterprise/
Disallow: /nonprofits-ngos
Disallow: /plans/try
Disallow: /es-us/

Sitemap: https://www.grammarly.com/sitemap.xml
Sitemap: https://www.grammarly.com/blog/sitemap_index.xml

sitemap.xml 200 OK
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.grammarly.com/ https://www.grammarly.com/

Consistent

A
Domain Intelligence
grammarly.com — via GoDaddy.com, LLC, 17 years old, hosted on AWS
PASS
grammarly.com — via GoDaddy.com, LLC, 17 years old, hosted on AWS
Warning::
Domain expires in 84 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 1, 2026
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
Info::
Hosting: AWS
Got: AS16509
Domain expiry

EXPIRED

July 1, 2026

SSL certificate

136 days

Issued by Amazon

Domain age

17 years

Registered July 1, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

108.139.10.76

Registrar

GoDaddy.com, LLC

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar GoDaddy.com, LLC
Created July 1, 2009 (17 years ago)
Expires July 1, 2026 (2 months)
Last Updated July 2, 2023
Name Servers ns-1221.awsdns-24.org, ns-1588.awsdns-06.co.uk, ns-422.awsdns-52.com, ns-835.awsdns-40.net
DNSSEC Not enabled
Hosting
IP Address 108.139.10.76
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

A+
HTTP Probe Timing
Total 202 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
186 ms
Total Time Total request time from DNS lookup through full response.
202 ms

Connection waterfall

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

Send Feedback