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

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

What TLS version does cyber.gov.au use?

cyber.gov.au uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does cyber.gov.au have DMARC configured?

Yes. cyber.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). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

Does cyber.gov.au have security headers configured?

cyber.gov.au has 0 of 0 recommended security headers. All recommended headers present.

Does cyber.gov.au use HSTS?

No. Could not fetch https://cyber.gov.au — connection failed or timed out.

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

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

Does cyber.gov.au have known CVE vulnerabilities?

No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.

Does cyber.gov.au have DNSSEC enabled?

Yes. Strengths: 2 nameservers configured (mira.ns.cloudflare.com., newt.ns.cloudflare.com.); DNSSEC enabled; Zone transfers properly restricted.

cyber.gov.au Security Report — Grade C (75/100)

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

Issues detected. Strengths: Certificate valid, 35 days remaining; Issued by Let's Encrypt; 1375 certificates logged in CT. Issues: Certificates issued by 11 different CAs (threshold: 8 for 1375 logged certs) — possible misconfiguration or shadow IT.

Conditional · 75/100

Shows meaningful security gaps that need attention. Positive signals: DNS Configuration, DMARC / Email Security, and MX Records & Mail Provider all passed. 4 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. 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

cyber.gov.au

75/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

4 items need attention

7 passed

Protect incoming email from downgrade attacks (MTA-STS)

MTA-STS & TLS Reporting

2–4 hours

This allows inbound email to be silently downgraded and intercepted without warning. This is a more advanced setting — skip it if you're not sure, and come back once the items above are handled. cyber.gov.au has no MTA-STS policy, which means an attacker positioned on the network path could silently downgrade incoming email from encrypted to unencrypted, with no warning to either side.

How to fix this

1This one usually needs a developer or your hosting provider's support team — it involves publishing a small text file on your website, not just a DNS record.

v=STSv1; id=20260101000000

version: STSv1 mode: testing mx: mail.cyber.gov.au max_age: 604800

2Add a TXT record with the name "_mta-sts" in your domain's DNS settings (check with whoever manages your website or domain registration) (id= just needs to be any unique short code you make up, e.g. today's date), with this value:

3Host a small policy file at https://mta-sts.cyber.gov.au/.well-known/mta-sts.txt with the content below.

4Start in "testing" mode for a couple of weeks, check the reports, then switch to "enforce".

MTA-STS guide

Report unlocked.

View all 7 passed checks

DNS Configuration

DMARC / Email Security

MX Records & Mail Provider

TLS Configuration

Known Breaches

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.cyber.gov.au ↗

Security page

cyber.gov.au/security ↗

cyber.gov.au/privacy ↗

DPA (Data Processing Agreement)

cyber.gov.au/dpa ↗

Updated recently

Subprocessors List

cyber.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

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: ★★★☆☆

Warn

Could not load cyber.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: ★☆☆☆☆

Issues

Strengths: Certificate valid, 35 days remaining; Issued by Let's Encrypt; 1375 certificates logged in CT. Issues: Certificates issued by 11 different CAs (threshold: 8 for 1375 logged certs) — possible misconfiguration or shadow IT.

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: ★☆☆☆☆