Skip to main content
DNS Tool
Executive's DNS Intelligence Brief
Generated 24 Jul 2026, 12:03 UTC
Duration 65.1s
Version v26.50.05-344-gc4825d920
Integrity 51f9bc3c4e336d2b243d785a75a8ec7c33f8080a723d3e29d0c4d314758ece932a99eb32f2ccc050e2aa011943fef9d8c65d6d624f1bbe0e2b8bc3814841bf06
Subject Domain
www.soa.ac.in

Executive's DNS Intelligence Brief

Board-level domain security assessment — www.soa.ac.in

24 Jul 2026, 12:03 UTC · 65.1s · SHA-3-512: 51f9✱✱✱✱ Verify ·Archived
Engineer
DNS Security & Trust Posture
Risk Level: High Risk
4 protocols configured, 5 not configured
3 recommendations
Analysis Confidence
MODERATE
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Email Spoofing
Vulnerable
Brand Impersonation
Not Set Up
DNS Tampering
Protected
Certificate Control
Configured
What Requires Attention
Recommended Publish an SPF record to authorize legitimate mail senders
Recommended Move DMARC policy from 'none' to 'quarantine' or 'reject'
Recommended Enable DMARC aggregate reporting (rua) for authentication visibility
The BIG Questions
Can this domain be impersonated by email? Partially DMARC present but no SPF
Can DNS itself be tampered with? Possible DNSSEC signed (DNSKEY + DS present), but chain-of-trust validation was not confirmed on our resolver path (AD flag unset, RFC 4035 §3.2.3) — protection depends on the client using a validating resolver
Can this brand be convincingly faked? Likely DMARC is monitor-only p=none (RFC 7489 §6.3) — spoofed mail is not blocked, brand faking is trivial
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 robots.txt present but does not block AI crawlers — content may be freely scraped
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 ERNET India
Email Provider Unknown
Web Hosting Squarespace
DNS Hosting Squarespace

Technical Findings

Email Authentication
Can this domain be impersonated by email? Partially — DMARC present but no SPF
SPF (Sender Policy) Missing
DMARC (Policy) Partial Policy: none Monitor Only
DKIM (Signatures) Not Detected
Mail Posture Limited Protection
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 Could Not Verify TLSA lookups did not complete — inconclusive, not a finding of absence
TLS-RPT (Reporting) Not Configured
Mail Transport Not Enforced Policy-assessed 2 probes
DNS Security
Can DNS itself be tampered with? Possible — DNSSEC signed (DNSKEY + DS present), but chain-of-trust validation was not confirmed on our resolver path (AD flag unset, RFC 4035 §3.2.3) — protection depends on the client using a validating resolver
DNSSEC Signed & Validated
DNSSEC configured (DNSKEY + DS records present) but AD flag not set — resolver did not confirm chain of trust validation (RFC 4035 §3.2.3). This may indicate a broken chain or a non-validating resolver path.
NS Delegation Healthy
Delegation Consistency 2 Issues
NS Fleet Health 2 Issues Diversity: Fair
Brand & Certificate Controls
Can this brand be convincingly faked? Likely — DMARC is monitor-only p=none (RFC 7489 §6.3) — spoofed mail is not blocked, brand faking is trivial
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 — robots.txt present but does not block AI crawlers — content may be freely scraped
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 Not Blocking No AI crawler restrictions found in 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 6 total Achievable: Moderate Risk
Critical Publish SPF Record

Add an SPF record to authorize mail servers for this domain.

High Upgrade DMARC from p=none

Your DMARC policy is monitor-only (p=none). Upgrade to p=quarantine or p=reject after reviewing reports to actively prevent spoofing.

Medium Add DMARC Aggregate Reporting

Add a rua= tag to receive aggregate DMARC reports. Without reporting, you cannot monitor authentication failures.

Low Add DANE/TLSA Records

DNSSEC is active — adding TLSA records enables DANE, which cryptographically binds your mail server certificates to DNS and prevents certificate-based MITM attacks.

Low Add TLS-RPT Reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.

Low Deploy MTA-STS

MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.

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.

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

51f9bc3c4e336d2b243d785a75a8ec7c33f8080a723d3e29d0c4d314758ece932a99eb32f2ccc050e2aa011943fef9d8c65d6d624f1bbe0e2b8bc3814841bf06
12 RFCs evaluated · DNS state at 24 Jul 2026, 12:03 UTC
Internet Archive — Permanent Record Wayback Machine

This analysis is permanently archived by the Internet Archive, providing independent third-party verification of DNS security posture at analysis time.

View Archived Snapshot