Engineer's DNS Intelligence Report
CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.
| Field | Value |
|---|---|
| Type | CAA |
| Host | dnstool.it-help.tech (root of domain — adjust CA to match your provider) |
| Value | 0 issue "letsencrypt.org" |
Email Security Methodology Can this domain be impersonated by email? No null MX indicates no-mail domain
SPF Record RFC 7208 §4 Verified
Valid SPF (no mail allowed) - domain declares it sends no email
DMARC Policy RFC 7489 §6.3 Verified
DMARC policy reject (100%) - excellent protection
pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.DKIM Records RFC 6376 §3.6 Verified
DKIM not discoverable via common selectors (large providers use rotating selectors)
l= tag body length vulnerability (attacker appends unsigned content to signed mail),
weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3),
DKIM replay attacks (re-sending legitimately signed messages at scale)
MTA-STS RFC 8461 §3 Verified
MTA-STS DNS record found but policy file inaccessible
MTA-STS policy enforcement is evaluated in Mail Transport Security below.
TLS-RPT RFC 8460 §3 Verified
TLS-RPT configured - receiving TLS delivery reports
DMARC External Reporting Authorization RFC 7489 §7.1
1 of 1 external reporting domains missing authorization
| External Domain | Authorization | Auth Record |
|---|---|---|
it-help.tech |
Unauthorized | — |
Third-Party Action Required
This authorization record must be created by the external reporting provider, not by you. Per RFC 7489 §7.1, the receiving domain must publish a TXT record to confirm it accepts DMARC reports from your domain.
What to do: Contact your DMARC reporting provider and ask them to publish the authorization TXT record shown above. If you use a managed DMARC service (e.g., Ondmarc, Dmarcian, Valimail), this is typically handled during onboarding — reach out to their support if the record is missing.
Impact if unresolved: Compliant receivers may silently discard aggregate or forensic reports destined for the unauthorized address, reducing your DMARC visibility.
DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No
No valid MX hosts — DANE check skipped
Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:
- DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
- MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).
Brand Security Can this brand be convincingly faked? Unlikely DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and BIMI with VMC provides verified brand identity in inboxes — email-based brand faking is effectively blocked; adding CAA records (RFC 8659) would further restrict certificate issuance for lookalike domains
BIMI BIMI Spec Verified Success No VMC SVG
BIMI configured - logo validated (VMC recommended for Gmail)
CAA RFC 8659 §4 Verified Warning
No CAA records found - any CA can issue certificates
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116
security.txt properly configured
Contact
Expires
Policy
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? Yes
AI governance signals observed
llms.txt llmstxt.org
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Content-Usage Directive IETF Draft
Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it.
Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Hidden Prompt Artifacts
Evidence Log (3 items)
| Type | Detail | Severity | Confidence |
|---|---|---|---|
llms_txt_found |
llms.txt file found providing structured LLM context | info | Observed |
llms_full_txt_found |
llms-full.txt also found (extended LLM context) | info | Observed |
robots_txt_no_ai_blocks |
robots.txt found but no AI-specific blocking directives | low | Observed |
Public Exposure Checks Are sensitive files or secrets exposed? No
No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.
Sources scanned (3)
- https://dnstool.it-help.tech/
- https://dnstool.it-help.tech/static/js/foundation.min.js?v=26.25.10
- https://dnstool.it-help.tech/static/js/main.min.js?v=26.25.10
What type of scan is this?
This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.
Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.
Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.
DNS Server Security Not Checked
No nameservers found — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.
| Check | Result | Detail |
|---|---|---|
| Zone Transfer (AXFR) | Denied | Not tested |
| Open Recursion | Disabled | Not tested |
| Nameserver Identity | Hidden | Not tested |
| Cache Snooping | Protected | Not tested |
Mail Transport Security Beta Is mail transport encrypted and verified? Partially TLS reporting is configured but no transport enforcement policy is active
No MX records found
Policy Assessment Primary
- TLS-RPT configured — domain monitors TLS delivery failures (RFC 8460)
Telemetry
mailto:tls-reports@it-help.techLive Probe Supplementary
Infrastructure Intelligence Who hosts this domain and what services power it? Direct
ASN / Network Success
Resolved 1 unique ASN(s) across 1 IP address(es)
| ASN | Name | Country |
|---|---|---|
AS396982 |
Google LLC | US |
34.111.179.208 → AS396982 (34.96.0.0/12)Edge / CDN Success
Domain appears to use direct origin hosting
SaaS TXT Footprint Success
No SaaS services detected
Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.
Domain Security Methodology Can DNS responses be tampered with in transit? No DNSSEC signed and validated, cryptographic chain of trust verified
DNSSEC RFC 4033 §2 Verified Inherited ECDSA P-256/SHA-256 Modern
DNSSEC inherited from parent zone (it-help.tech) - DNS responses are authenticated
NS Delegation Subdomain
Subdomain within it-help.tech zone - no separate delegation needed
Traffic & Routing Where does this domain's traffic actually terminate?
AIPv4 Address
AAAAIPv6 Address
SRVServices
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? None found
How did we find these?No subdomains found via Certificate Transparency logs, DNS probing, or CNAME chain traversal for this domain. No TLS certificates have been issued and no common service names resolve for subdomains of dnstool.it-help.tech.
DNS Evidence Diff Side-by-side comparison
34.111.179.208
34.111.179.208
v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:security@it-help.tech;
v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:security@it-help.tech;
v=STSv1; id=20260208
v=STSv1; id=20260208
0 .
0 .
v=TLSRPTv1; rua=mailto:tls-reports@it-help.tech
v=TLSRPTv1; rua=mailto:tls-reports@it-help.tech
replit-verify=f2c73519-b3f3-4c33-90b1-699f833acae8
replit-verify=f2c73519-b3f3-4c33-90b1-699f833acae8
v=spf1 -all
v=spf1 -all
DNS History Timeline BETA
When was a record added, removed, or changed — and could that change be the problem?
Confirm Your Email Configuration
This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.
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.
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.
47bf52f39550ddb8cd597fd5c2c0f063196ce4d4f07b17558a39c737df1653a5888eec00d5769bd6340b3550d0020f1d69f66975dca04b8f38a7369b7d0674fd
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).
cat dns-intelligence-dnstool.it-help.tech.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-dnstool.it-help.tech.jsonpython3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-dnstool.it-help.tech.json','rb').read()).hexdigest())"sha3sum -a 512 dns-intelligence-dnstool.it-help.tech.json.sha3 file or the checksum API at /api/analysis/3757/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 dnstool.it-help.tech. 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
dig +noall +answer dnstool.it-help.tech Adig +noall +answer dnstool.it-help.tech AAAAdig +noall +answer dnstool.it-help.tech MXdig +noall +answer dnstool.it-help.tech NSdig +noall +answer dnstool.it-help.tech TXTEmail Authentication
dig +short dnstool.it-help.tech TXT | grep -i spfdig +short _dmarc.dnstool.it-help.tech TXTdig +short default._domainkey.dnstool.it-help.tech TXTdig +short google._domainkey.dnstool.it-help.tech TXTdig +short selector1._domainkey.dnstool.it-help.tech TXTdig +short selector2._domainkey.dnstool.it-help.tech TXTDomain Security
dig +dnssec +noall +answer dnstool.it-help.tech DNSKEYdig +noall +answer dnstool.it-help.tech DSdig +dnssec +cd dnstool.it-help.tech A @1.1.1.1Transport Security
dig +noall +answer _25._tcp.MX_HOST TLSAdig +short _mta-sts.dnstool.it-help.tech TXTcurl -sL https://mta-sts.dnstool.it-help.tech/.well-known/mta-sts.txtdig +short _smtp._tls.dnstool.it-help.tech TXTBrand & Trust
dig +short default._bimi.dnstool.it-help.tech TXTdig +noall +answer dnstool.it-help.tech CAADNS Records
dig +noall +answer dnstool.it-help.tech HTTPSDomain Security
dig +noall +answer dnstool.it-help.tech CDSInfrastructure Intelligence
curl -sL 'https://rdap.org/domain/dnstool.it-help.tech' | python3 -m json.tool | head -50curl -s 'https://crt.sh/?q=%25.dnstool.it-help.tech&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20curl -sL https://dnstool.it-help.tech/.well-known/security.txt | head -20AI Surface
curl -sI https://dnstool.it-help.tech/llms.txt | head -5curl -s https://dnstool.it-help.tech/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
dig +short 208.179.111.34.origin.asn.cymru.com TXTdig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Appendix: Verification Commands
DNS Records
dig +noall +answer dnstool.it-help.tech Adig +noall +answer dnstool.it-help.tech AAAAdig +noall +answer dnstool.it-help.tech MXdig +noall +answer dnstool.it-help.tech NSdig +noall +answer dnstool.it-help.tech TXTEmail Authentication
dig +short dnstool.it-help.tech TXT | grep -i spfdig +short _dmarc.dnstool.it-help.tech TXTdig +short default._domainkey.dnstool.it-help.tech TXTdig +short google._domainkey.dnstool.it-help.tech TXTdig +short selector1._domainkey.dnstool.it-help.tech TXTdig +short selector2._domainkey.dnstool.it-help.tech TXTDomain Security
dig +dnssec +noall +answer dnstool.it-help.tech DNSKEYdig +noall +answer dnstool.it-help.tech DSdig +dnssec +cd dnstool.it-help.tech A @1.1.1.1Transport Security
dig +noall +answer _25._tcp.MX_HOST TLSAdig +short _mta-sts.dnstool.it-help.tech TXTcurl -sL https://mta-sts.dnstool.it-help.tech/.well-known/mta-sts.txtdig +short _smtp._tls.dnstool.it-help.tech TXTBrand & Trust
dig +short default._bimi.dnstool.it-help.tech TXTdig +noall +answer dnstool.it-help.tech CAADNS Records
dig +noall +answer dnstool.it-help.tech HTTPSDomain Security
dig +noall +answer dnstool.it-help.tech CDSInfrastructure Intelligence
curl -sL 'https://rdap.org/domain/dnstool.it-help.tech' | python3 -m json.tool | head -50curl -s 'https://crt.sh/?q=%25.dnstool.it-help.tech&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20curl -sL https://dnstool.it-help.tech/.well-known/security.txt | head -20AI Surface
curl -sI https://dnstool.it-help.tech/llms.txt | head -5curl -s https://dnstool.it-help.tech/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
dig +short 208.179.111.34.origin.asn.cymru.com TXT