Skip to content
https://www.asana.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 Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
DNS Records
2 A records, 28 ms lookup
REVIEW
2 A records, 28 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 3.33.186.135, 15.197.167.90
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a05:d01c:9e6:f102::1f5
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: asana.netlifyglobalcdn.com
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: 28 ms
Got: 28 ms
A3.33.186.135, 15.197.167.90
AAAA2a05:d01c:9e6:f102::1f5
CNAMEasana.netlifyglobalcdn.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 28 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.

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)

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.asana.com/
200https://asana.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.asana.com/ → https://www.asana.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
Netlify
REVIEW
Netlify
Info::
Site is served via Netlify CDN
Got: x-nf-request-id: 01KNMS4N78QKWCEFW083TEHM9X
CDN Detected: Netlify
Provider Netlify Evidence x-nf-request-id: 01KNMS4N78QKWCEFW083TEHM9X
A
Redirect Chain
1 redirect(s), 420 ms total
PASS
1 redirect(s), 420 ms total
Info::
Single redirect
Got: https://www.asana.com → https://asana.com/ (301)
Info::
WWW normalization redirect

https://www.asana.com

81 ms · HTTP/1.1

301

https://asana.com/

339 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.asana.com30181 msHTTP/1.1Netlify
2https://asana.com/200339 msHTTP/1.1Netlify

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (26 ms)
PASS
IPv6 reachable (26 ms)
Info::
IPv6 is configured and reachable at 2a05:d01c:9e6:f102::1f5
Got: 26 ms connect
IPv6 Ready
AAAA Records 2a05:d01c:9e6:f102::1f5 Connection Reachable (26 ms)
A+
Crawlability
robots.txt present, sitemap with 16 URLs
PASS
robots.txt present, sitemap with 16 URLs
Info::
robots.txt is present
Got: 547 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 16 entries
Info::
Sitemap index with 16 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 547 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /apply/*/*
Disallow: /apply/
Disallow: /en/
Disallow: /admin/
Disallow: /asanapedia/
Disallow: /internal/
Disallow: /nike/
Disallow: /trust.php
Disallow: /sitemap-extended
Disallow: /ebook/
Disallow: /resources/marketing/full
Disallow: /resources/thank-you
Disallow: /resources/media/
Allow: /assets/dist/css/asana-apps.css
Allow: /assets/dist/css/asana-guide.css
Allow: /assets/dist/
Disallow: /terms/hipaa-requirements-and-limitations
Disallow: /terms/business-associate-addendum
Sitemap: https://asana.com/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 16 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
asana.com — via Amazon Registrar, Inc., 17 years, 5 months old, hosted on AWS
PASS
asana.com — via Amazon Registrar, Inc., 17 years, 5 months old, hosted on AWS
Info::
Domain registered until Jan 21, 2027 (9 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: Amazon Registrar, Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

193 days

January 21, 2027

SSL certificate

63 days

Issued by Let's Encrypt

Domain age

17 years, 5 months

Registered January 21, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

15.197.167.90

Registrar

Amazon Registrar, Inc.

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 Amazon Registrar, Inc.
Created January 21, 2009 (17 years, 5 months ago)
Expires January 21, 2027 (9 months)
Last Updated December 17, 2025
Name Servers ns-1105.awsdns-10.org, ns-1990.awsdns-56.co.uk, ns-236.awsdns-29.com, ns-810.awsdns-37.net
DNSSEC Not enabled
Hosting
IP Address 15.197.167.90
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

A+
HTTP Probe Timing
Total 131 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
44 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.
59 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
131 ms
Total Time Total request time from DNS lookup through full response.
132 ms

Connection waterfall

DNS Lookup 44 ms TCP Connect 1 ms TLS Handshake 59 ms Server Processing 28 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