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
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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.
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# This robots.txt content is autogenerated
User-agent: ia_archiver
Disallow: /
User-agent: *
Allow: /wiki/
Disallow: /sr/
Disallow: /si/
Disallow: /charts
Disallow: /secure/ConfigureReport.jspa
Disallow: /secure/ConfigureReport!default.jspa
Disallow: /secure/admin/
Disallow: /l/cx/
Disallow: /login
Disallow: /logout
BTLS Certificate Expiry & Recommendations175 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
A+DNS Records1 A records, 38 ms lookupPASS
| A | 13.227.180.4 |
| AAAA | — |
| CNAME | — |
| NS | ns-1339.awsdns-39.org, ns-573.awsdns-07.net, ns-1977.awsdns-55.co.uk, ns-110.awsdns-13.com |
| MX | — |
| TXT | google-site-verification=RcQzq2eURg5hALm4AJx83xamzfGRTnnPJNE9feT4RT8 SPF v=spf1 include:_spf.atlassian.net include:mail-us.atlassian.net include:mail-eu.... google-site-verification=yq6ec0SWleFz2nse2rgP5Q7sznwCHE6Kz5xYlHdXozM _y9v5ywzhhllg47h8catqr2ah3t5s3j4 google-site-verification=OyBu9JKNiNvdQuVQEWjXouXR0Gpk4K2WMZLeq3i_sfY google-site-verification=WpeKPXgdFvut3EnXYV5bdhGILreS4EQH9g7eOYmEWdU google-site-verification=5kaM72FkLAQ72an-enpRdA0RoMezFPNDVstAVJ2zzNE google-site-verification=mbA1ipHOqyfuvt0Kg_zsiICOUkUmLQAIjRvlPVKln6g d25ka488dfqyj6.cloudfront.net google-site-verification=crpcLWBHzgUpszF01N1mEBQxQyjLHLGLde2xTznJ9bI google-site-verification=OGjH-MHnCqvQnCvbwfFjx18uywUBboMJznZuLNK9EX0 google-site-verification=I35-DPIfQpm1DJDty6A-CPqZZuJH3VFBVdDfTX9oQ-w yandex-verification: e0b60c84b0265951 |
| 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.
ARedirect Chain1 redirect(s), 411 ms totalPASS
https://atlassian.net
47 ms · HTTP/1.1
https://www.atlassian.com/software
364 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://atlassian.net | 301 | 47 ms | HTTP/1.1 | AtlassianEdge |
| 2 | https://www.atlassian.com/software | 200 | 364 ms | HTTP/1.1 | AtlassianEdge |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceatlassian.net — via MarkMonitor Inc., 25 years, 5 months old, hosted on AWSPASS
279 days
March 19, 2027
175 days
Issued by Amazon
25 years, 5 months
Registered March 19, 2001
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
13.227.180.4
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice