Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations194 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- 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
ADNS Records1 A records, 138 ms lookupPASS
| A | 13.227.180.4 |
| AAAA | — |
| CNAME | — |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
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'.
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 ChainNo redirects — direct accessPASS
https://www.atlassian.com
197 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.atlassian.com | 200 | 197 ms | HTTP/1.1 | AtlassianEdge |
A+Crawlabilityrobots.txt present, sitemap with 8054 URLsPASS
User-agent: *
Disallow: /blog/author/*
Disallow: /blog/tag/*
Disallow: /blog/it-teams/tam-day-summit-3-big-takeaways-2/attachment/tam-day
Disallow: /dam/jcr:261696c7-3570-4760-b2a6-b69264c2a2db
Disallow: /dam/jcr:d493cbe0-67e8-4aa5-8972-b41046099254/Lean%20ITSM%20Whitepaper.pdf$
Disallow: /dam/jcr:b549786a-5967-4603-91eb-16a9d8902061/cPrime_SAFewhitepaper_0829_125636.pdf$
Disallow: /dam/jcr:7b30c258-5588-43a5-ba8a-cd1d1cce64cd/Enterprise%20Success%20Package%20One-pager%20Updated%20.pdf$
Disallow: /dam/jcr:1c950f05-9161-4b6b-9fe3-be3e7b1f0412/Jira%20Align%20Enterprise%20Success%20Package%20One-Pager.pdf$
Disallow: */purchase/*
Disallow: */variants/*
Allow: /purchase/price-comparison$
User-agent: atlassian-bot
Disallow: /blog/author/*
Disallow: /blog/tag/*
Disallow: /blog/search/*
Disallow: /blog/archives/*
Disallow: /blog/*/page/*
Disallow: /company/careers/detail/*
# Block all localized paths from being crawled
Disallow: /ja/*
Disallow: /fr/*
Disallow: /de/*
Disallow: /es/*
Disallow: /br/*
Disallow: /zh/*
Disallow: /ko/*
Disallow: /ru/*
Disallow: /pl/*
Disallow: /it/*
Disallow: /nl/*
Disallow: /fi/*
Disallow: /hu/*
Disallow: /ro/*
Disallow: /cs/*
Sitemap: https://www.atlassian.com/sitemap.xml
# Sitemap for Blog
Sitemap: https://www.atlassian.com/blog/post-sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligenceatlassian.com — via MarkMonitor Inc., 25 years, 4 months old, hosted on AWSPASS
279 days
March 19, 2027
194 days
Issued by Amazon
25 years, 4 months
Registered March 19, 2001
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
3.160.90.35
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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