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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
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
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 633 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 633 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# Allow everything
User-agent: *
Disallow: /search?
Disallow: /reset?
Disallow: /confirm?
Disallow: /confirmDelete?
# Allow /recommend deny /username/recommend
Disallow: ^/*/recommend
Disallow: */add-card?
Disallow: */login?
Disallow: */signup?
Disallow: /forgot$
Disallow: /statement/
Disallow: /boardinvited/
Disallow: /invite/
Disallow: /organizationinvited/
Disallow: /boardInviteDeclined/
Disallow: /organizationInviteDeclined/
Disallow: /associate/
Disallow: /not-supported.html
Disallow: /static/
Disallow: /1/
Disallow: /c/
Disallow: /b/
Disallow: /u/
Disallow: /w/
Allow: /

Sitemap: https://trello.com/sitemap-index.xml.gz

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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.trello.com/
200https://trello.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
4 A records, 38 ms lookup
PASS
4 A records, 38 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 3.165.190.118, 3.165.190.56, 3.165.190.129, 3.165.190.47
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: trello.com
Info::
4 nameserver(s) configured
Got: ns-1442.awsdns-52.org, ns-402.awsdns-50.com, ns-722.awsdns-26.net, ns-2013.awsdns-59.co.uk
Info::
2 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: 38 ms
Got: 38 ms
A3.165.190.118, 3.165.190.56, 3.165.190.129, 3.165.190.47
AAAA
CNAMEtrello.com
NSns-1442.awsdns-52.org, ns-402.awsdns-50.com, ns-722.awsdns-26.net, ns-2013.awsdns-59.co.uk
MX
10 mxb-001d9801.gslb.pphosted.com
10 mxa-001d9801.gslb.pphosted.com
TXT
SPF v=spf1 include:_spf.google.com include:_spf.salesforce.com include:spemail.trell...
google-site-verification=j10V2FxDCOpk-ZtvXbt0csUYbGo4uttk0VIeNN3pMwQ
google-site-verification=L1Pv1rpciXhbLcwV1z84F6fdeNpGMIDd4nrgAzCQncc
google-site-verification=UqQbR3bkx0DW0mTjn4zpy-pFaTOtklFFLgVJPLpWBfg
google-site-verification=klLlb7yZqSKsDzIEQ_Ck9G8vJZrZUYSl7G6SYm5ugaU
google-site-verification=lFRc2QYcvrD1x-JP-sbqyEHEVFTzLiYr_s5TMwqDPGE
atlassian-domain-verification=ZRphniOpyvhHV76mRmxnLkHJVrKnbeOIxmhbxb8PF6AarX0Fyp...
google-site-verification=XiTuMrGYNDAcJ3h6FgJn-qK1wWhcRCTrwK7ihP4lgzQ
facebook-domain-verification=5g7n6qixu6oqonzuw4igcyn2fd52yi
google-site-verification=m3SBLzut__3UbFT85xIcXyZs4CsOKfX6MrdByMh6xSM
mailru-verification: 26cd15930108c82c
slack-domain-verification=IQyaWt1Bt2nVwCvOsgj2ObAap344ynM5bV6C8zlZ
CAALookup not available with standard resolver
Resolved in 38 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), 249 ms total
PASS
1 redirect(s), 249 ms total
Info::
Single redirect
Got: https://www.trello.com → https://trello.com/ (301)
Info::
WWW normalization redirect

https://www.trello.com

140 ms · HTTP/1.1

301

https://trello.com/

109 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.trello.com301140 msHTTP/1.1AtlassianEdge
2https://trello.com/200109 msHTTP/1.1AtlassianEdge

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
trello.com — via MarkMonitor Inc., 21 years, 11 months old, hosted on AWS
PASS
trello.com — via MarkMonitor Inc., 21 years, 11 months old, hosted on AWS
Info::
Domain registered until Jun 1, 2027 (1 years, 1 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: MarkMonitor Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

324 days

June 1, 2027

SSL certificate

184 days

Issued by Amazon

Domain age

21 years, 11 months

Registered August 20, 2004

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.165.190.56

Registrar

MarkMonitor Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar MarkMonitor Inc.
Created August 20, 2004 (21 years, 11 months ago)
Expires June 1, 2027 (1 years, 1 months)
Last Updated April 7, 2026
Name Servers ns-1442.awsdns-52.org, ns-2013.awsdns-59.co.uk, ns-402.awsdns-50.com, ns-722.awsdns-26.net
DNSSEC Enabled
Hosting
IP Address 3.165.190.56
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)
A+
HTTP Probe Timing
Total 173 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
33 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
36 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
174 ms
Total Time Total request time from DNS lookup through full response.
174 ms

Connection waterfall

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

Send Feedback