Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 17 Feb 2026, 14:20 UTC
Duration 40.6s
Version v26.19.21
Integrity abf4e5ac48b08b8752aa19c8421b1260c1b5b61b63672232d665d77072bc959bfca253d3f54620a0051ced91c3fb8925adcfd51153a60260b699c6ad26b13db5
Subject Domain
clinicbilling.com

Engineer's DNS Intelligence Report

clinicbilling.com
17 Feb 2026, 14:20 UTC · 40.6s ·v26.19.21 · SHA-3-512: abf4✱✱✱✱ Verify ·Cross-Referenced
Executive Topology Replay
Recon Mode Snapshot Re-analyze New Domain
Engineer workspace · evidence preserved

Read the verdict first. Descend only as far as the incident requires.

This report keeps the complete technical record while separating decision, interpretation, evidence, and raw reproduction into a stable disclosure gradient.

L0PostureL1InterpretationL2EvidenceL3Raw & reproduce
Hurry path
MX & Routing Subdomains DNSSEC What changed
KEYBOARD !1@2#3$4%5^6 jump to that section · esc back to the verdict

Non-existent / Undelegated Domain

Domain is not delegated or has no DNS records. This may be an unused subdomain or unregistered domain.

What This Means

  • No authoritative DNS data is available for this domain
  • Security posture cannot be evaluated without DNS records
  • The domain may never have been registered, or has expired
  • If this is your domain, check your registrar to confirm it's active
Try Another Domain
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.

abf4e5ac48b08b8752aa19c8421b1260c1b5b61b63672232d665d77072bc959bfca253d3f54620a0051ced91c3fb8925adcfd51153a60260b699c6ad26b13db5
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 17 Feb 2026, 14:20 UTC.
Download Raw Intelligence Download Checksum (.sha3) Cross-Reference Verification

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-clinicbilling.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-clinicbilling.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-clinicbilling.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-clinicbilling.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/1195/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 clinicbilling.com. 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 clinicbilling.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer clinicbilling.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer clinicbilling.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer clinicbilling.com NS
Query TXT records RFC 1035 
dig +noall +answer clinicbilling.com TXT

Email Authentication

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

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer clinicbilling.com DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer clinicbilling.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd clinicbilling.com 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.clinicbilling.com TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.clinicbilling.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.clinicbilling.com TXT

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/clinicbilling.com' | python3 -m json.tool | head -50
Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.clinicbilling.com&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://clinicbilling.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://clinicbilling.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://clinicbilling.com/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 Gold · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Gold 15673 runs
DKIM
Gold 15463 runs
DMARC
Gold 15654 runs
DANE/TLSA
Gold 15445 runs
DNSSEC
Gold 15632 runs
BIMI
Gold 15460 runs
MTA-STS
Gold 15481 runs
TLS-RPT
Gold 15496 runs
CAA
Gold 15493 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

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

Email Authentication

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

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer clinicbilling.com DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer clinicbilling.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd clinicbilling.com 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.clinicbilling.com TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.clinicbilling.com/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.clinicbilling.com TXT

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer clinicbilling.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer clinicbilling.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/clinicbilling.com' | python3 -m json.tool | head -50
Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.clinicbilling.com&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://clinicbilling.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://clinicbilling.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://clinicbilling.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

0s

Running Real-Time Scan Telemetry

Most scans complete in less than one minute. Some may take longer.

Markers represent known resolver locations. Anycast routing selects the nearest node — exact routing is internal to each provider.

Pipeline nodes reflect live data as each analysis phase completes.

Telemetry Log 0 polls