Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 21 Feb 2026, 22:42 UTC
Duration 53.9s
Version v26.23.50
Integrity 94f9986f628c356117a8a5a9e37f5a245c7ae236c9e4a7062e92061e9e14b1de5e1af25a04c8bf923dafdba4965ca24aa55b23f99eed781a2a855e97644af04f
Subject Domain
blauw.com

Engineer's DNS Intelligence Report

blauw.com
21 Feb 2026, 22:42 UTC · 53.9s ·v26.23.50 · SHA-3-512: 94f9✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint Barracuda 3 SaaS Services
DNS Security & Trust Posture
Risk Level: Medium Risk
4 protocols configured, 4 not configured, 1 unavailable on provider Why we go beyond letter grades
1 recommendation 1 monitoring
Suggested Scanner Configuration Medium Confidence
Based on 8 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 37.1s, 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.
Email Spoofing
Partial
Brand Impersonation
Not Setup
DNS Tampering
Protected
Certificate Control
Open
Recommended
Enable DMARC aggregate reporting (rua) for authentication visibility
Monitoring
DMARC record has configuration warnings — review recommended
Configured
SPF (hard fail), DMARC (with warnings), DKIM, DNSSEC
Not Configured
MTA-STS, TLS-RPT, BIMI, CAA
Unavailable on Provider
DANE
Priority Actions 5 total Achievable posture: Secure
Medium Add DMARC Aggregate Reporting

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

Aggregate reports show who is sending mail as your domain and whether it passes authentication.
TypeTXT
Host_dmarc.blauw.com (add to existing DMARC record)
Valuerua=mailto:dmarc-reports@blauw.com
RFC 7489 §7.1
Medium Increase DMARC Coverage

Your DMARC policy only applies to 40% of mail. Increase pct to 100 for full protection.

RFC 7489 §6.3
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.
TypeCAA
Hostblauw.com (root of domain — adjust CA to match your provider)
Value0 issue "letsencrypt.org"
RFC 8659
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.

TLS-RPT sends you reports about TLS connection failures to your mail servers.
TypeTXT
Host_smtp._tls.blauw.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@blauw.com
RFC 8460
Low Deploy MTA-STS

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

MTA-STS tells sending servers to require TLS when delivering mail to your domain.
TypeTXT
Host_mta-sts.blauw.com (MTA-STS policy record)
Valuev=STSv1; id=blauw.com
RFC 8461
Registrar (RDAP) OBSERVED LIVE
Realtime Register B.V.
Where domain was purchased
Email Service Provider INFERRED
Microsoft 365
Moderately Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? Partially DMARC quarantine at limited percentage

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? Yes
Success -all 6/10 lookups

SPF valid with strict enforcement (-all), 6/10 lookups

v=spf1 ip4:213.208.244.178/32 ip4:92.65.130.66/32 include:autotask.net include:spf.protection.outlook.com include:spf.ess.de.barracudanetworks.com include:_spf.act-on.net include:_spf.atlassian.net include:spf-eu.emailsignatures365.com -all
RFC 7489 §10.1: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC enforcement is partial (quarantine). -all may preempt DKIM/DMARC evaluation at some receivers. Consider p=reject for full enforcement; ~all is more DMARC-compatible.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Quarantined, not rejected
Warning p=quarantine 40% enforced

DMARC quarantine but only 40% enforced - partial protection

v=DMARC1; p=quarantine; ruf=mailto:DMARC-ruf@blauw.com; fo=1; pct=40;
Only 40% of mail subject to policy
No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing
No aggregate reporting (rua) configured — you won't receive reports about authentication results and potential abuse
Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports
RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
Monitoring Posture Note: Quarantine sequesters authentication failures while preserving full DMARC forensic telemetry (RFC 7489 §7). Some organizations maintain quarantine rather than reject as a deliberate monitoring strategy — failed messages are processed and reported but sequestered from the inbox. See NIST SP 800-177 Rev. 1 for enforcement tradeoffs.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace 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.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Yes — verified
Found

Found DKIM records for 4 selector(s)

Mail routed through Barracuda (security gateway) — DKIM signed by Microsoft 365 (sending platform). This is a standard enterprise architecture.
s1._domainkey SendGrid
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw1gU64wM331J2x42nJ5l0VWV9mz2yyXOQwlgqvQ5eOkANWTV43m7GSCUU9MBBKHDpm6+8o9nY+5vm506tZSqv06iEKhL3O6jjMeYBg44TrdMJ+5i0V2m9oxo7gSFBsZLKWec19eULbn2egjBTwSFRrRGpLL8QTFE7r3kIL/ILwtNQttRYbi+LUB0YZGowoPJarkeq8viT9vPy1Xvx8jl+rFM4EdqO10KEjBqkF2lrsfhec03XNooI8EnNhvD3nl++KaZm7/yHiZal05VxoLajbUDmC89iK7H/JpGOpaOqFT9YXLrkvqv9S1ehYg5UpaMMkedAxb8yP6EZAYxBEBEewIDAQAB
s2._domainkey SendGrid
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC8tvSmzHnj/KkHIVAuonmai05ZFiat3Js8GETYTxg0Pfb3773i53A56TIx89vrodwSgVPFTQFqQ1Tg/KOpQM6YlCYFWpirTqtwBBs7ty8tVV6e1qgFkucClqdsdkyg9FY/+orKQ51ee1z8RVt4XhEi7dQJQAMFJMn06/hPHR1UKQIDAQAB
selector1._domainkey Microsoft 365
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArjLVF+HnjksfMPJaZqONK/4/wydYINtSD11BxUVSsNm6ZAX35YRqmQHh5Sc5w5IpvoY/0fquu2EXuLX0i7fbS4PtCz6oVU1p9W/kV6M+k7e8pwfhOgSi/FYGAv7f5pvWtxdHjpNU44Q6rgtITwdULLQh9o/t36MWHTxISb+LvK7J/gTigVP5zvilZd3ECqEn+K1x5AgCQThRLM8LZ3PrfKOJhO34fybVLzcazIvXEn7nB6wMM5rLR0MBZVtv1JmfgRNwdZ1Gv5sZ+7IRQIdRAX14OSYK4Dc0va8Wz8TtRU15yDMjZlnCbhSpMe1R8lOHjskczIT8GrGqDAVVkskMYQIDAQAB;
selector2._domainkey Microsoft 365
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyOQqYtc/z3A0fPPV0JVxT1lzMIr85gLYSMinAToPyYjWF8/oyqePr/yOMv5fRlQn/qep6S1XSiwyD4p2Yxrg5CQGESzZ8YrNdtylHfvloAw7oJLMSn/EW1WGu5H8DmYDpL5sZNLFnTluooB2u5yrT8qjNGqHyeNdLuwGWUsnwR013RQHOlQEH700FY/4WC2xA2vtMv2D4WFqqvAKk+P3bO9Oulwk0fqr56+empYGd6OZQVDfishgFZ1ZHvbzg6EpoWJw9RJfBErnwH7QwylZcSN7sWck5UOcmORuWoQxP+mqDU/f5kL0pskVoJJQ7U3rsL6eCmg5Ba/zs4kTNRId0QIDAQAB;
RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).
Known Vulnerabilities: DKIM 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

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — Barracuda does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Barracuda

Barracuda is a security gateway with shared MX infrastructure. It does not publish per-customer TLSA records.

Recommended alternative: MTA-STS

Email Transport Security

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).
This domain has neither DANE nor MTA-STS. Since Barracuda does not support inbound DANE, deploy MTA-STS (RFC 8461) to enforce TLS and protect against downgrade attacks.

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? Likely DMARC quarantine flags but does not reject spoofed mail (RFC 7489 §6.3) — no BIMI or CAA (RFC 8659) reinforcement leaves brand impersonation largely unaddressed

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Verified Warning

Does this domain restrict who can issue TLS certificates? No

No CAA records found - any CA can issue certificates

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116

No security.txt found

A security.txt file at /.well-known/security.txt provides security researchers with a standardized way to report vulnerabilities. See securitytxt.org for a generator.
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

No AI governance measures detected

llms.txt llmstxt.org
Is this domain publishing AI-readable brand context? No
No llms.txt found
No llms-full.txt found
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Are AI crawlers explicitly allowed or blocked? Not blocked
No AI crawler blocking observed — no blocking directives found in robots.txt
Content-Usage Directive IETF Draft
Does the site express AI content-usage preferences? Not Configured
No Content-Usage directive detected. The IETF AI Preferences working group is developing a 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.
Example: Add 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
Is this site trying to manipulate AI recommendations? No
No AI recommendation poisoning indicators found
Hidden Prompt Artifacts
Is hidden prompt-injection text present in the source? No
No hidden prompt-like artifacts detected
Evidence Log (1 item)
TypeDetailSeverityConfidence
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.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
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.

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

No transport encryption policy detected — mail delivery relies on opportunistic TLS

Policy Assessment Primary

No transport enforcement policies detected. Mail delivery relies on opportunistic STARTTLS, which is vulnerable to downgrade attacks (RFC 3207). Consider deploying MTA-STS (RFC 8461) or DANE (RFC 7672).

Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
Skipped — SMTP port 25 not reachable from this host — outbound port 25 is likely blocked by the hosting provider. Transport security is assessed via DNS policy records, which is the standards-aligned primary method per NIST SP 800-177 Rev. 1.
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)

ASNNameCountry
AS209242 Cloudflare London, LLC US
IPv4 Mappings:
198.202.211.1 → AS209242 (198.202.211.0/24)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 3 services

3 SaaS services detected via DNS TXT verification records

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.

ServiceVerification Record
Google Workspace google-site-verification=7RuHa9iLYQdlq6PBhLw4xsAI7MWtEjazi7C4aTzhook
Atlassian atlassian-domain-verification=TozlHTrYUqMYu4cvxOoJaT9I1zQjVsJAe7QQSUzuWtKmye7CfV...
Microsoft 365 MS=ms34400650
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 Signed RSA/SHA-256 Adequate

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)

Algorithm Observation: RSA/SHA-256 — MUST implement, widely deployed (RFC 8624 §3.1)
All current DNSSEC algorithms use classical cryptography. Post-quantum DNSSEC standards are in active IETF development (draft-sheth-pqc-dnssec-strategy) but no PQC algorithms have been standardized for DNSSEC yet.
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):
65029 8 2 F9EFBD7E272BA77313E720DCCCEAE8FD43ABA6A587B099E12B9B001721B259A8

NS Delegation Verified

3 nameserver(s) configured

Nameservers: ns1.argewebhosting.eu ns2.argewebhosting.com ns3.argewebhosting.nl
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [44a017ee4ed3891a9ea7444854283e77 78e30145150acb90cc19fc0f49eb5c47 MS=ms34400650 google-site-verification=7RuHa9iLYQdlq6PBhLw4xsAI7MWtEjazi7C4aTzhook google-site-verification=atoxvyJBsq7Uls2fP-lozYIw8-MJDmESPtl_S-3yzoU google-site-verification=ohGKGHbS0TuMQF_hDpunuM7i6MPD1jrnNlHsNzQ3GZE lvc1j4j389guro9ob1fgtr14vu openai-domain-verification=dv-2yk37nnYcj3uNNt0SrdJIkl5]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

198.202.211.1
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

20 d301495.b.ess.de.barracudanetworks.com.
10 d301495.a.ess.de.barracudanetworks.com.
Priority + mail server for email delivery
Microsoft 365

SRVServices

_sip._tls: 100 1 443 sipdir.online.lync.com.
_imaps._tcp: 0 0 993 arg-plplcl16.argewebhosting.nl.
_sipfederationtls._tcp: 100 1 5061 sipfed.online.lync.com.
SIP, XMPP, or other service endpoints
Web: Reachable (1 IPv4, 0 IPv6) Mail: 2 servers Services: 3 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 16 subdomains discovered
How did we find these?
CT logs unavailable 16 current 0 expired 9 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
app.marketsimulator.blauw.com CT Log Current — 4 2026-01-31T12:45:50 Let's Encrypt
autodiscover.blauw.com DNS Current autodiscover.outlook.com 1 2025-04-06 GoDaddy.com, Inc.
biva.blauw.com CT Log Current ghs.googlehosted.com 2 2026-01-13T09:14:30 Google Trust Services
blauwtalk.blauw.com CT Log Current blauwtalkdashboard-c5b9czb3egbpdpee.westeurope-01.azurewebsites.net 1 2026-02-17T00:00:00 DigiCert Inc
ftp.blauw.com DNS Current — 1 2025-04-06 GoDaddy.com, Inc.
images.blauw.com DNS Current — 1 2025-04-06 GoDaddy.com, Inc.
marketing.blauw.com CT Log Current blauw.actonservice.com 3 2025-02-10T13:23:06 GoDaddy.com, Inc.
marketsimulator2.blauw.com CT Log Current blauwmarketsimulator-b5hycngahxg2bqbu.westeurope-01.azurewebsites.net 2 2026-01-05T00:00:00 DigiCert, Inc.
mijn.blauw.com CT Log Current — 4 2026-02-20T07:12:53 Let's Encrypt
owa.blauw.com DNS Current autodiscover.outlook.com 1 2025-04-06 GoDaddy.com, Inc.
pop3.blauw.com DNS Current owa.blauw.com 1 2025-04-06 GoDaddy.com, Inc.
rmia.blauw.com CT Log Current witty-moss-06dbf4803.3.azurestaticapps.net 5 2026-02-18T00:00:00 DigiCert Inc, DigiCert, Inc.
sftp.blauw.com DNS Current — 1 2025-04-06 GoDaddy.com, Inc.
werkenbij.blauw.com CT Log Current — 4 2026-02-07T20:57:15 Let's Encrypt
www.blauw.com CT Log Current cdn.webflow.com 11 2026-01-24T08:07:59 Google Trust Services
www.marketing.blauw.com CT Log Current — 3 2025-02-10T13:23:06 GoDaddy.com, Inc.
Export Recon (CSV)
Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
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 Synchronized 1 / 1 records
198.202.211.1
198.202.211.1
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.blauw.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=quarantine; ruf=mailto:DMARC-ruf@blauw.com; fo=1; pct=40;
v=DMARC1; p=quarantine; ruf=mailto:DMARC-ruf@blauw.com; fo=1; pct=40;
MX RFC 5321 Synchronized 2 / 2 records
20 d301495.b.ess.de.barracudanetworks.com.
10 d301495.a.ess.de.barracudanetworks.com.
10 d301495.a.ess.de.barracudanetworks.com.
20 d301495.b.ess.de.barracudanetworks.com.
NS RFC 1035 Synchronized 3 / 3 records
ns3.argewebhosting.nl.
ns1.argewebhosting.eu.
ns2.argewebhosting.com.
ns3.argewebhosting.nl.
ns1.argewebhosting.eu.
ns2.argewebhosting.com.
SOA RFC 1035 Synchronized 1 / 1 records
ns1.argewebhosting.eu. migratie.argeweb.nl. 2026021200 10800 3600 604800 10800
ns1.argewebhosting.eu. migratie.argeweb.nl. 2026021200 10800 3600 604800 10800
TXT RFC 7208 §4 Synchronized 10 / 10 records
google-site-verification=7RuHa9iLYQdlq6PBhLw4xsAI7MWtEjazi7C4aTzhook
44a017ee4ed3891a9ea7444854283e77
google-site-verification=ohGKGHbS0TuMQF_hDpunuM7i6MPD1jrnNlHsNzQ3GZE
78e30145150acb90cc19fc0f49eb5c47
google-site-verification=atoxvyJBsq7Uls2fP-lozYIw8-MJDmESPtl_S-3yzoU
MS=ms34400650
78e30145150acb90cc19fc0f49eb5c47
atlassian-domain-verification=TozlHTrYUqMYu4cvxOoJaT9I1zQjVsJAe7QQSUzuWtKmye7CfVYg1a3M1nNDwKmZ
lvc1j4j389guro9ob1fgtr14vu
lvc1j4j389guro9ob1fgtr14vu
atlassian-domain-verification=TozlHTrYUqMYu4cvxOoJaT9I1zQjVsJAe7QQSUzuWtKmye7CfVYg1a3M1nNDwKmZ
google-site-verification=ohGKGHbS0TuMQF_hDpunuM7i6MPD1jrnNlHsNzQ3GZE
44a017ee4ed3891a9ea7444854283e77
openai-domain-verification=dv-2yk37nnYcj3uNNt0SrdJIkl5
v=spf1 ip4:213.208.244.178/32 ip4:92.65.130.66/32 include:autotask.net include:spf.protection.outlook.com include:spf.ess.de.barracudanetworks.com include:_spf.act-on.net include:_spf.atlassian.net include:spf-eu.emailsignatures365.com -all
google-site-verification=atoxvyJBsq7Uls2fP-lozYIw8-MJDmESPtl_S-3yzoU
openai-domain-verification=dv-2yk37nnYcj3uNNt0SrdJIkl5
google-site-verification=7RuHa9iLYQdlq6PBhLw4xsAI7MWtEjazi7C4aTzhook
MS=ms34400650
v=spf1 ip4:213.208.244.178/32 ip4:92.65.130.66/32 include:autotask.net include:spf.protection.outlook.com include:spf.ess.de.barracudanetworks.com include:_spf.act-on.net include:_spf.atlassian.net include:spf-eu.emailsignatures365.com -all
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

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

Analyze Another Domain

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.

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.

94f9986f628c356117a8a5a9e37f5a245c7ae236c9e4a7062e92061e9e14b1de5e1af25a04c8bf923dafdba4965ca24aa55b23f99eed781a2a855e97644af04f
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 21 Feb 2026, 22:42 UTC.
Download Raw Intelligence Download Checksum (.sha3)

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

Email Authentication

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

Domain Security

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

Transport Security

Check TLSA record for d301495.b.ess.de.barracudanetworks.com RFC 7672 
dig +noall +answer _25._tcp.d301495.b.ess.de.barracudanetworks.com TLSA
Check TLSA record for d301495.a.ess.de.barracudanetworks.com RFC 7672 
dig +noall +answer _25._tcp.d301495.a.ess.de.barracudanetworks.com TLSA
Verify TLS certificate on primary MX (d301495.b.ess.de.barracudanetworks.com) RFC 6698 
openssl s_client -starttls smtp -connect d301495.b.ess.de.barracudanetworks.com:25 -servername d301495.b.ess.de.barracudanetworks.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.blauw.com TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.blauw.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.blauw.com TXT

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/blauw.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (d301495.b.ess.de.barracudanetworks.com) RFC 3207 
openssl s_client -starttls smtp -connect d301495.b.ess.de.barracudanetworks.com:25 -servername d301495.b.ess.de.barracudanetworks.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.blauw.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://blauw.com/.well-known/security.txt | head -20

AI Surface

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

Infrastructure Intelligence

ASN lookup for 198.202.211.1 (Team Cymru) 
dig +short 1.211.202.198.origin.asn.cymru.com TXT
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 4843 runs
DKIM
Verified 4662 runs
DMARC
Verified 4827 runs
DANE/TLSA
Verified 4646 runs
DNSSEC
Verified 4824 runs
BIMI
Verified 4661 runs
MTA-STS
Verified 4664 runs
TLS-RPT
Verified 4666 runs
CAA
Verified 4658 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 blauw.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer blauw.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer blauw.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer blauw.com NS
Query TXT records (RFC 1035) 
dig +noall +answer blauw.com TXT

Email Authentication

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

Domain Security

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

Transport Security

Check TLSA record for d301495.b.ess.de.barracudanetworks.com (RFC 7672) 
dig +noall +answer _25._tcp.d301495.b.ess.de.barracudanetworks.com TLSA
Check TLSA record for d301495.a.ess.de.barracudanetworks.com (RFC 7672) 
dig +noall +answer _25._tcp.d301495.a.ess.de.barracudanetworks.com TLSA
Verify TLS certificate on primary MX (d301495.b.ess.de.barracudanetworks.com) (RFC 6698) 
openssl s_client -starttls smtp -connect d301495.b.ess.de.barracudanetworks.com:25 -servername d301495.b.ess.de.barracudanetworks.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.blauw.com TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.blauw.com/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.blauw.com TXT

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/blauw.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (d301495.b.ess.de.barracudanetworks.com) (RFC 3207) 
openssl s_client -starttls smtp -connect d301495.b.ess.de.barracudanetworks.com:25 -servername d301495.b.ess.de.barracudanetworks.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.blauw.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://blauw.com/.well-known/security.txt | head -20

AI Surface

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

Infrastructure Intelligence

ASN lookup for 198.202.211.1 (Team Cymru) 
dig +short 1.211.202.198.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

blauw.com

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.