Is ato.gov.au safe to use as a vendor?

ato.gov.au scored 72/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 7 checks passed, 6 warnings, 2 critical issues across 15 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does ato.gov.au use?

ato.gov.au uses TLSv1.3 with TLS_AES_128_GCM_SHA256. TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does ato.gov.au have DMARC configured?

Yes. ato.gov.au's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: cm).

Does ato.gov.au have SPF configured?

Yes. SPF record found: v=spf1 ip4:180.149.192.213 ip4:180.149.192.214 ip4:180.149.192.215 ip4:180.149.1...

Does ato.gov.au have security headers configured?

ato.gov.au has 2 of 5 recommended security headers. Present: CSP, X-Frame-Options. Missing: X-Content-Type-Options, Referrer-Policy, Permissions-Policy.

Has ato.gov.au been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does ato.gov.au have known CVE vulnerabilities?

Detected technologies: AkamaiGHost. (AkamaiGHost detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.

ato.gov.au Security Report — Grade C- (72/100)

Q: Does ato.gov.au use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

Q: Is ato.gov.au's SSL certificate valid?

Issues detected. Strengths: Issued by DigiCert Inc. Issues: Certificate expires in 25 days — renewal recommended.

Q: Does ato.gov.au have DNSSEC enabled?

No. Strengths: 6 nameservers configured (a18-64.akam.net., a1-75.akam.net., a8-66.akam.net., a12-67.akam.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

C-

Conditional · 72/100

Shows significant security gaps that need urgent attention. Positive signals: DMARC / Email Security, MX Records & Mail Provider, and TLS Configuration all passed. 7 action items identified, including 0 critical. The issues point to real architectural gaps, not just configuration tweaks. A focused remediation effort of 1–2 days could address all findings.

Trust Score Trend

→ No change 1 scan · Last scanned February 24, 2026

Score

100 75 50 25 0

C-

ato.gov.au

72/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

Pro subscribers only

ISO 27001

Certificate not on file

3rd party · accredited body

Pro subscribers only

GDPR

DPA not on file

Self-reported

Pro subscribers only

CCPA

Self-reported

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

7 items need attention

7 passed

Turn on HSTS (forces browsers to always use HTTPS)

HSTS Header

< 1 hour

This puts visitor logins and session data at risk of interception on untrusted networks. ato.gov.au doesn't send the HSTS header, so a browser can still be tricked into connecting over plain, unencrypted HTTP instead of HTTPS — an attacker on the same network (e.g. public wifi) can exploit that gap to intercept traffic. Turning HSTS on tells every browser "always use HTTPS for this site, no exceptions."

PCI-DSS 4.0Req 6.4.1

Required application security controls

NIST 800-53SC-8

Transmission confidentiality and integrity

How to fix this

1Add this response header to your site. If you manage your own server (nginx, Apache, IIS) or a CDN like Cloudflare, add it in that config. If your site is on a managed platform (Wix, Squarespace, Shopify, WordPress.com), search their help center for "custom headers" or ask their support — most support it, though a few don't.

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

2Before adding it, make sure every subdomain (not just the main site) also works over HTTPS — HSTS applies site-wide.

3Confirm it's live: search "http header checker" and enter ato.gov.au.

4Once confirmed, submit the domain at hstspreload.org so browsers enforce HTTPS even on a user's very first visit.

HSTS guide

Report unlocked.

View all 7 passed checks

DMARC / Email Security

MX Records & Mail Provider

TLS Configuration

Known Breaches

Cookie Security

TLS Protocol Support

CVE Exposure

Company Signals

Claim profile →

Operational risk

Low

11 yrs operating. Well-funded

Lynxradar · Composite signal

Last funding

$40B

Series F · Mar 2025 · SoftBank-led

Crunchbase ↗

Employees

~3,000

+40% YoY growth

LinkedIn ↗

Trust Resources

Claim profile →

Trust Center

trust.ato.gov.au ↗

Security page

ato.gov.au/security ↗

ato.gov.au/privacy ↗

DPA (Data Processing Agreement)

ato.gov.au/dpa ↗

Updated recently

Subprocessors List

ato.gov.au/policies/subprocessors ↗

Similar companies

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Blocking Issues

Not enabled

Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

Likelihood: ★★★☆☆

Impact: ★★★★☆

2/5 present

Missing: X-Content-Type-Options, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 6 nameservers configured (a18-64.akam.net., a1-75.akam.net., a8-66.akam.net., a12-67.akam.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Issues

Strengths: Issued by DigiCert Inc. Issues: Certificate expires in 25 days — renewal recommended.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆

Warn

Could not load ato.gov.au's homepage to detect its e-commerce platform, payment processor, or CDN.

Best Practice

Warn

No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆