Skip to content
https://www.crowdin.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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
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.crowdin.com/
200https://crowdin.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

227
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
2 A records, 36 ms lookup
PASS
2 A records, 36 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 3.223.15.136, 54.163.150.3
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: crowdin.com
Info::
4 nameserver(s) configured
Got: ns-630.awsdns-14.net, ns-365.awsdns-45.com, ns-1716.awsdns-22.co.uk, ns-1437.awsdns-51.org
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: 36 ms
Got: 36 ms
A3.223.15.136, 54.163.150.3
AAAA
CNAMEcrowdin.com
NSns-630.awsdns-14.net, ns-365.awsdns-45.com, ns-1716.awsdns-22.co.uk, ns-1437.awsdns-51.org
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx3.googlemail.com
30 aspmx2.googlemail.com
TXT
SPF v=spf1 include:_spf.google.com include:mail.crowdin.com include:servers.mcsv.net...
cursor-domain-verification-ja5jab=l6xFJlm7f6LRKedaq6QtUs0ll
anthropic-domain-verification-bd6s69=60d95mcfNKRyKFREwnINXcf
anthropic-domain-verification-wkv17e=1xGWZrk3WVzi8zZ8Murd1poU8
ahrefs-site-verification_e4fe0989e69379efbb46cf7779c2b9b6e14e29f36778153cf4bd5db...
atlassian-domain-verification=RgaTXSIDEtOqgnC9DJ/zs39nh4OmpBfJi6tODHG43nl9Xb6qax...
h1-domain-verification=YQxrcqy5r7QdR3yxBhDfg3kLEqZnC3yME1TNfiq1DwUDfpX4
google-site-verification=BNFZRZ7iSH0j_yvQ3EeGDi0VmBZNLehlLTCl19HL4Jc
CAALookup not available with standard resolver
Resolved in 36 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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
1 redirect(s), 718 ms total
PASS
1 redirect(s), 718 ms total
Info::
Single redirect
Got: https://www.crowdin.com → https://crowdin.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 718 ms total
Got: 718 ms

https://www.crowdin.com

296 ms · HTTP/1.1

301

https://crowdin.com/

422 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.crowdin.com301296 msHTTP/1.1nginx
2https://crowdin.com/200422 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 333 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 333 B Sitemaps referenced 1 User-agents http://Mail.RU, Yandex, * Blocking No — crawling allowed
User-agent: http://Mail.RU
Disallow: /

User-agent: Yandex
Disallow: /

User-agent: *
Disallow: /app
Disallow: /join
Disallow: /login
Disallow: /settings
Disallow: /backend
Disallow: /download
Disallow: /case-studies/*
Disallow: /*/js/lib/magic/*
Disallow: /blog/post/*
Disallow: /translate

Sitemap: https://crowdin.com/sitemap.xml

sitemap.xml 200 OK
A+
Domain Intelligence
crowdin.com — via GoDaddy.com, LLC, 17 years, 4 months old, hosted on AWS
PASS
crowdin.com — via GoDaddy.com, LLC, 17 years, 4 months old, hosted on AWS
Info::
Domain registered until Feb 7, 2033 (6 years, 11 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
Info::
Hosting: AWS
Got: AS14618
Domain expiry

2402 days

February 7, 2033

SSL certificate

227 days

Issued by Amazon

Domain age

17 years, 4 months

Registered February 7, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

54.163.150.3

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
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar GoDaddy.com, LLC
Created February 7, 2009 (17 years, 4 months ago)
Expires February 7, 2033 (6 years, 11 months)
Last Updated March 20, 2023
Name Servers ns-1437.awsdns-51.org, ns-1716.awsdns-22.co.uk, ns-365.awsdns-45.com, ns-630.awsdns-14.net
DNSSEC Not enabled
Hosting
IP Address 54.163.150.3
ASN AS14618 (AMAZON-AES - 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

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

Connection waterfall

DNS Lookup 60 ms TCP Connect 98 ms TLS Handshake 99 ms Server Processing 100 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