Skip to main content
Registry Zone Health Intelligencecom.au is a shared registry suffix.
This report focuses on zone infrastructure health: DNSSEC signing, nameserver diversity, certificate authority policy, and delegation security. Email authentication protocols (SPF, DMARC, DKIM) are not applicable to registry suffixes — they apply to domains registered under this zone.
Registry operators, ICANN, and ccTLD authorities can use this view to assess zone security posture.

Registry Zone Health Report

com.au
18 Feb 2026, 00:02 UTC · 4.9s ·v26.19.38 · SHA-3-512: 7e9f✱✱✱✱ Verify
Recon ModeRecon Mode Snapshot Re-analyze New Domain
Footprint
Suggested Scanner Configuration High Confidence
Based on 17 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 40.9s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures.
RFC 8767
Suggestions require explicit approval before applying. No automatic changes will be made.
Registry Zone Health
DNSSEC: Success CAA: Not Set 0 Nameservers
Zone infrastructure protocols applicable to registry suffixes
Email Spoofing
Vulnerable
Brand Impersonation
Not Setup
DNS Tampering
Protected
Certificate Control
Open
Recommended
Enable DMARC aggregate reporting (rua) for authentication visibility
Monitoring
SPF configured with soft fail (~all) — consider upgrading to hard fail (-all), DMARC record has configuration warnings — review recommended, DKIM signing inferred from provider — could not directly verify selector
Configured
SPF, DMARC (with warnings), DKIM (inferred via Unknown), DNSSEC
Not Configured
MTA-STS, TLS-RPT, BIMI, DANE, CAA
Priority Actions Achievable posture: Secure
high Add DMARC Reject for No-Mail Domain

This domain has no MX records and appears to be a website-only domain. A DMARC reject policy tells receiving mail servers to reject any email claiming to be from your domain.

Instructs receiving servers to reject all email from this domain — no legitimate mail is expected.
FieldValue
TypeTXT
Host_dmarc.com.au
Valuev=DMARC1; p=reject; sp=reject; adkim=s; aspf=s;
high Lock Down SPF for No-Mail Domain

This domain has no MX records and appears to be a website-only domain. Publishing a strict SPF record explicitly declares that no servers are authorized to send email, preventing attackers from spoofing your domain.

Explicitly declares no servers are authorized to send email from this domain.
FieldValue
TypeTXT
Hostcom.au
Valuev=spf1 -all
Low Add CAA Records

CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.

CAA constrains which CAs can issue certificates for this domain.
FieldValue
TypeCAA
Hostcom.au (root of domain — adjust CA to match your provider)
Value0 issue "letsencrypt.org"
Registrar (WHOIS) OBSERVED LIVE
auDA Internal (9999) (Registrant: .au Domain Administration Limited)
Where domain was purchased
Email Service Provider
Unknown
Moderately Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited



Zone Signing & DNSSEC Methodology Is this zone cryptographically signed? YES DNSSEC signed and validated, cryptographic chain of trust verified

DNSSEC RFC 4033 §2 Verified Signed RSA/SHA-256

DNSSEC fully configured and validated — AD (Authenticated Data) flag set by resolver 8.8.8.8 confirming cryptographic chain of trust from root to zone (RFC 4035 §3.2.3)

Chain of trust: Root → TLD → Domain. DNS responses are authenticated and tamper-proof.
AD Flag: Validated - Resolver (8.8.8.8) confirmed cryptographic signatures
DS Record (at registrar):
14185 8 2 9394BEA09F5EBD91384AA5CD0397A6B395FD2B299C7912979243CD689BA387DB

NS Delegation Verified Match

NS delegation verified - 5 nameserver(s) match parent zone

Parent zone delegation matches domain's NS records. No delegation drift detected.
Nameservers: a.au q.au r.au s.au t.au
Multi-Resolver Verification Recon: Consensus reached - 4 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
Subdomain Discovery Not Applicable
Certificate Transparency subdomain enumeration is not applicable for registry suffixes. For com.au, CT logs would show registered domains under this zone rather than organizational subdomains. To analyze a specific domain's exposure, scan a registrable domain like example.com.au.
Δ Changes Detected: SOA Resolver ≠ Authoritative (TTL / CDN rotation / recent change)
Risk: Low - typically resolves within TTL
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A 0 / 0 records
No records
No records
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
MX RFC 5321 0 / 0 records
No records
No records
NS RFC 1035 Synchronized 5 / 5 records
t.au.
a.au.
q.au.
q.au.
a.au.
r.au.
s.au.
s.au.
r.au.
t.au.
SOA RFC 1035 Propagating 1 / 1 records
q.au. hostmaster.donuts.email. 1771372609 7200 900 1209600 3600
q.au. hostmaster.donuts.email. 1771372719 7200 900 1209600 3600
TXT RFC 7208 §4 0 / 0 records
No records
No records
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

Analyze Another Domain

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

7e9f8b3e8e2cf5bc204b4353044c96a490567fcaae00e71803056a3b80fa644872933dd4b2d33201a8813c9d62ce30dfed58e91e9509eddc2cf17f35938fffd8
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 18 Feb 2026, 00:02 UTC.

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL)
cat dns-intelligence-com.au.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-com.au.json
Python 3 (cross-platform)
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-com.au.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+)
sha3sum -a 512 dns-intelligence-com.au.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/1602/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for com.au. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035
dig +noall +answer com.au A
Query AAAA records (IPv6) RFC 1035
dig +noall +answer com.au AAAA
Query MX records (mail servers) RFC 1035
dig +noall +answer com.au MX
Query NS records (nameservers) RFC 1035
dig +noall +answer com.au NS
Query TXT records RFC 1035
dig +noall +answer com.au TXT

Email Authentication

Check SPF record RFC 7208
dig +short com.au TXT | grep -i spf
Check DMARC policy RFC 7489
dig +short _dmarc.com.au TXT
Check DKIM key for selector 'default' RFC 6376
dig +short default._domainkey.com.au TXT
Check DKIM key for selector 'google' RFC 6376
dig +short google._domainkey.com.au TXT
Check DKIM key for selector 'selector1' RFC 6376
dig +short selector1._domainkey.com.au TXT
Check DKIM key for selector 'selector2' RFC 6376
dig +short selector2._domainkey.com.au TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035
dig +dnssec +noall +answer com.au DNSKEY
Check DNSSEC DS records RFC 4035
dig +noall +answer com.au DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035
dig +dnssec +cd com.au A @1.1.1.1

Transport Security

Check TLSA record (replace MX_HOST with actual MX) RFC 7672
dig +noall +answer _25._tcp.MX_HOST TLSA
Check MTA-STS DNS record RFC 8461
dig +short _mta-sts.com.au TXT
Fetch MTA-STS policy file RFC 8461
curl -sL https://mta-sts.com.au/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460
dig +short _smtp._tls.com.au TXT

Brand & Trust

Check BIMI record BIMI Draft
dig +short default._bimi.com.au TXT
Check CAA records (certificate authority authorization) RFC 8659
dig +noall +answer com.au CAA

DNS Records

Check HTTPS/SVCB records RFC 9460
dig +noall +answer com.au HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344
dig +noall +answer com.au CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083
curl -sL 'https://rdap.org/domain/com.au' | python3 -m json.tool | head -50
Search Certificate Transparency logs RFC 6962
curl -s 'https://crt.sh/?q=%25.com.au&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt RFC 9116
curl -sL https://com.au/.well-known/security.txt | head -20

AI Surface

Check for llms.txt
curl -sI https://com.au/llms.txt | head -5
Check robots.txt for AI crawler rules
curl -s https://com.au/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'
Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine Verified · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Verified 4850 runs
DKIM
Verified 4669 runs
DMARC
Verified 4834 runs
DANE/TLSA
Verified 4653 runs
DNSSEC
Verified 4831 runs
BIMI
Verified 4668 runs
MTA-STS
Verified 4671 runs
TLS-RPT
Verified 4673 runs
CAA
Verified 4665 runs
Maturity: Development Verified Consistent Gold Gold Master
Running Multi-Source Intelligence Audit

com.au

0s
DNS records — Cloudflare, Google, Quad9, OpenDNS, DNS4EU
Email auth — SPF, DMARC, DKIM selectors
DNSSEC chain of trust & DANE/TLSA
Certificate Transparency & subdomain discovery
SMTP transport & STARTTLS verification
MTA-STS, TLS-RPT, BIMI, CAA
Registrar & infrastructure analysis
Intelligence Classification & Interpretation

Every result includes terminal commands you can run to independently verify the underlying data. No proprietary magic.