Executive's DNS Intelligence Brief
DNS Security & Trust Posture
Risk Level:
Low Risk
4 protocols configured, 5 not configured
Email Spoofing
Protected
Brand Impersonation
Not Set Up
DNS Tampering
Unsigned
Certificate Control
Configured
What Requires Attention
No urgent actions detected. Domain security posture is well-maintained.
The BIG Questions
Can this domain be impersonated by email?
No
null MX indicates no-mail domain
Can DNS itself be tampered with?
Possible
DNSSEC is not deployed, DNS responses are not cryptographically verified
Can this brand be convincingly faked?
Unlikely
DMARC reject policy blocks email spoofing, but no BIMI brand verification — brand faking via other vectors remains possible
Is mail transport encryption enforced?
No
No MTA-STS or DANE — mail transport encryption is opportunistic only
Is certificate issuance controlled?
Yes
CAA records restrict which certificate authorities may issue certificates
Does this domain publish AI agent instructions?
No
No llms.txt file detected — AI models have no structured instructions for this domain
Is AI crawling of our content controlled?
No
No robots.txt found — AI crawlers have unrestricted access
Has someone manipulated AI recommendations about us?
No
No indicators of AI recommendation manipulation found
Are there hidden AI prompts on our site?
No
No hidden prompt artifacts found in page source
Domain Overview
Registrar
HOSTINGER operations, UAB
Email Provider
No Mail Domain
Web Hosting
Unknown
DNS Hosting
Unknown
Technical Findings
Email Authentication
Can this domain be impersonated by email?
No
— null MX indicates no-mail domain
SPF (Sender Policy)
Configured
DMARC (Policy)
Configured
Policy: reject
DKIM (Signatures)
Not Detected
Mail Posture
No Mail Observed
Mail Transport Security
Is mail transport encryption enforced?
No
— No MTA-STS or DANE — mail transport encryption is opportunistic only
MTA-STS
Partial
DANE / TLSA
Hosted Provider
No valid MX hosts — DANE check skipped
TLS-RPT (Reporting)
Not Configured
Mail Transport
Not Enforced
Policy-assessed
DNS Security
Can DNS itself be tampered with?
Possible
— DNSSEC is not deployed, DNS responses are not cryptographically verified
DNSSEC
Partial
DNSSEC not configured - DNS responses are unsigned
NS Delegation
Healthy
Brand & Certificate Controls
Can this brand be convincingly faked?
Unlikely
— DMARC reject policy blocks email spoofing, but no BIMI brand verification — brand faking via other vectors remains possible
Is certificate issuance controlled?
Yes
— CAA records restrict which certificate authorities may issue certificates
BIMI (Brand Logo)
Not Configured
CAA (Certificate)
Configured
AI Surface Scanner Scanned
Does this domain publish AI agent instructions?
No
— No llms.txt file detected — AI models have no structured instructions for this domain
Is AI crawling of our content controlled?
No
— No robots.txt found — AI crawlers have unrestricted access
Has someone manipulated AI recommendations about us?
No
— No indicators of AI recommendation manipulation found
Are there hidden AI prompts on our site?
No
— No hidden prompt artifacts found in page source
LLM Context File
Not Found
No llms.txt file detected
AI Crawler Governance
No robots.txt
Poisoning Indicators
None Found
No AI recommendation poisoning indicators detected
Hidden Prompt Artifacts
None Found
No hidden prompt artifacts detected
Public Exposure
Clear
No secrets detected in publicly accessible source
Priority Actions 1 total Achievable: Hardened
Medium
Enable DNSSEC
DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.
Appendix — Additional Resources
Full technical details including raw DNS records, DKIM public keys, IP/ASN mappings, resolver consensus evidence, and verification commands are available in the Engineer's DNS Intelligence Report.
Verify Report Integrity SHA-3-512 Has this report been tampered with? Verify below
Tamper-evident fingerprint binding this analysis to its data, domain, timestamp, and tool version.
3abfd8d977d317e9e5e32c4ba5cf4097e8cd536f6c64696786c8b1ca8dde816c8267e3d2ef824c32d3be2e5dc22b041f66b6ed2896a47c383fa1648cba54ccf4
12 RFCs evaluated · DNS state at 17 Feb 2026, 04:31 UTC