Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 10 Mar 2026, 15:20 UTC
Duration 27.9s
Version v26.35.35
Integrity efcaae3cfba0dee7ebf4986240c42d7a8b42bff0f53a66f643293660868c2b5a4c0117b415e7b7353d5ab0df14239b3d8e3eb1cf7e64b97be877bec7569088ec
Subject Domain
reconfirm.com

Engineer's DNS Intelligence Report

reconfirm.com
10 Mar 2026, 15:20 UTC · 27.9s ·v26.35.35 · SHA-3-512: efca✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint Microsoft 365 1 SaaS Service
DNS Security & Trust Posture
Risk Level: Low Risk
6 protocols configured, 2 not configured, 1 unavailable on provider Why we go beyond letter grades
Analysis Confidence (ICD 203)
MODERATE 64/100
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 57% Currency 73/100 Maturity verified
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Intelligence Currency
Data Currency: Adequate 73/100
ICuAE Details
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Degraded
DNS data shows some aging or gaps — consider re-scanning for critical decisions

The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.

Record Type Observed TTL Typical TTL Severity Context
TXT 270s 1 hour (3600s) high TXT TTL is below typical — observed 270s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
NS 21539s 1 day (86400s) medium NS TTL is below typical — observed 21539s, typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
A 5 minutes (300s) 1 hour (3600s) high A TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
AAAA 5 minutes (300s) 1 hour (3600s) high AAAA TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
MX 5 minutes (300s) 1 hour (3600s) high MX TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.

Big Picture Questions

  • How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
  • Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
  • Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
  • Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.
Tune TTL for reconfirm.com
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) Note: Some DNS providers (e.g., AWS Route 53 alias records, Cloudflare proxied records) enforce fixed TTLs that cannot be modified. If a finding targets a record you cannot edit, it reflects the observed value rather than a configuration error on your part.
Primary NS ns0.transip.net
Serial 2026030902
Admin hostmaster.transip.nl
Provider Unknown
Timer Value RFC 1912 Range
Refresh86400s1,200–43,200s (20 min – 12 hrs)
Retry1800sFraction of Refresh
Expire2419200s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)300s300–86,400s (5 min – 1 day)
All SOA timer values are within RFC 1912 recommended ranges.
Email Spoofing
Protected
Brand Impersonation
Not Setup
DNS Tampering
Protected
Certificate Control
Open
Configured
SPF, DMARC (reject), DKIM, MTA-STS, TLS-RPT, DNSSEC
Not Configured
BIMI, CAA
Unavailable on Provider
DANE
Priority Actions Achievable posture: Secure
Low Add BIMI Record

Your domain has DMARC reject — you qualify for BIMI, which displays your brand logo in receiving email clients that support it (Gmail, Apple Mail, Yahoo).

BIMI displays your verified brand logo next to your emails in supporting mail clients.
TypeTXT
Hostdefault._bimi.reconfirm.com (BIMI default record)
Valuev=BIMI1; l=https://reconfirm.com/brand/logo.svg
RFC 9495
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
Hostreconfirm.com (root of domain — adjust CA to match your provider)
Value0 issue "letsencrypt.org"
RFC 8659
Registrar (RDAP) OBSERVED LIVE
Key-Systems GmbH
Where domain was purchased
Email Service Provider INFERRED
Microsoft 365
Strongly 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? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Verified

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

SPF valid with industry-standard soft fail (~all), 1/10 lookups

v=spf1 include:spf.protection.outlook.com ~all
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)
~all is the industry standard. Google, Apple, and most providers default to soft fail. CISA (BOD 18-01) and RFC 7489 confirm that DMARC policy — not SPF alone — is the primary enforcement control. Using ~all allows DKIM to be evaluated before a DMARC decision is made. This domain uses ~all + DMARC reject: the strongest compatible security stance, aligned with CISA and RFC guidance.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Yes — reject policy
Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; sp=reject; rua=mailto:f0c7af39@in.mailhardener.com,mailto:f598f966@in.mailhardener.com; aspf=r; adkim=s; fo=1; ruf=mailto:dmarc@reconfirm.nl
Alignment: SPF relaxed DKIM strict sp=reject
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 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.
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 2048-bit

Found DKIM for 4 selector(s) with strong keys (2048-bit)

s1._domainkey SendGrid 2048-bit Adequate
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6U16ihPgw+/Q/TF0lPyH262GRaKeMPauZKTxEHQIGggKjGvGy/vKJxUjfEsikAlEDbrUqZuAro67XixI8n+fUYpFvAMtCB6r/JQeFWuWUZX9oumKcgsuBCXLUtXVYVw2XnLUrGyjqK3j8NKZWaNQhtKTFGhbFXQMyFuFqz1oaDUjagy7Q6JmcoUtRdNAtuxjWp8N7Wy86YwctnCYGE9vjcWp5XAzx5Zi9Gy8xoskbQHDXEZmwCGghQtGT73pMmCY5LlTA85MSuKE1gp5Tu2ekrGc6Rg5XwBKA+go48qQgBNl7iLjWSve+wrLg2k7x6oXIAmJA58rV4+kJpjj4mNqGwIDAQAB
s2._domainkey SendGrid 2048-bit Adequate
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnZHyelcFTODZotJiTCcF6Hapz5V2Tx0TWV/gVnpDEBYoOusaY4DSKVkqIlTub7VeEh5xAch2tt/DklArfhUeNVcCdeSlDdqND7FWKEigyJGDQ1+jDYeDCqgI6ywA6qrRiSs29YzfBjZLxYUiGMf5+v0uxQQj+ki0q1HKrKaUQLqT/zs8NpuQBVv12q2E8SbCIGnnojcZcS8UHD20uqO/uQ2QK67x47iFzeT5BeVplKQp4csmYBYQOaoX74RUQeLwMyyl8UZNKnrTKQeritLbwqfQZeutD8sZS6QGVJmt8+C+bwq61pTnHk5hhQ+5rcR3gBohO0yIc5DL8M/WwgeG7QIDAQAB
selector1._domainkey Microsoft 365 2048-bit Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4myIcWQZ7ti5ulX7y/JKyJOg0JKTlTT0ZkCqCZWr/Td0e0lmFmfq9sQaoPvQr2KbHABNfxbz4vn3PnKNvxEK5V6wOMI+cvwh5zdC5ehTtDCelM08aUhSBW2XLT+/P9lEBq6KYYUANuRlLVsZuBkp/MP/MsWx1UsfsR26P83HWBeXrJ9syX91h1VyM3Qo7b/d9qgiObSk19buyw02YHtJsZeYGTK0BKycQ1zJ/DnM96F+D5IPO1WF0w544nXgL3p57+a/zJE3ZIcVHGbLsY3zUM+U6ZRrNGG0QTW3hWLl6UFvfzZYdwdrSrOpppf02tFs53p9UvsZ3vNWqQ0LZAWDjQIDAQAB;
selector2._domainkey Microsoft 365 2048-bit Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuDNCabRuq1oupsxw0W9tu/fz1vGHabHo38M36xdeQ7OKNouScvN+RAQlThOi9bI4m9NlxGsyMzfqmIBos3Zz2YeKIN9HWhkdm+F2Lf3A+MorMcm1VtAfOKe6SEWeSZN+J9g78EepPnxfWuXrytDNueCosnzvaHTXbSSyfMdQcihCeczffgAw4PTdffVCcXC1fqShZnenht4rNOiBMO5pePWFCRsEzZTKsb/XAawNTZcXlNHDZhP5Fx7fYt5x995KGvLrB27vydj8fFy1/7YKP5G6ubr38htL9MxzT8mCWzlyYaTLKKNRRGdCfA4ybOUvauvTFov39gtgwhUVuWLE9QIDAQAB;
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? No — TLS enforced
Success ENFORCE Policy Verified

MTA-STS enforced - TLS required for 2 mail server(s)

v=STSv1; id=20032023T211300;
Policy Details:
  • Mode: enforce
  • Max Age: 7 days (604800 seconds)
  • MX Patterns: reconfirm-com.mail.protection.outlook.com, *.protection.outlook.com

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

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? Yes — reports configured
Success

TLS-RPT configured - receiving TLS delivery reports

v=TLSRPTv1; rua=mailto:f0c7af39@in.mailhardener.com

DMARC External Reporting Authorization RFC 7489 §7.1

Are external report receivers authorized? Yes — all authorized
Success

All 2 external reporting domains properly authorized

External Domain Authorization Auth Record
in.mailhardener.com Authorized v=DMARC1;
reconfirm.nl Authorized v=DMARC1;
DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? via MTA-STS (CA)
RFC 7672 §3 RFC 6698 §2 Not Available

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

DANE not deployable on Microsoft 365

Microsoft 365 does not support DANE for inbound mail. Microsoft uses its own certificate pinning mechanism.

Recommended alternative: MTA-STS (already configured)

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 uses MTA-STS — the best available option for Microsoft 365. Since Microsoft 365 does not support inbound DANE, MTA-STS is the strongest transport security this domain can deploy. MTA-STS enforces TLS via HTTPS-based policy, protecting against downgrade attacks (RFC 8461).

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? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3), but no BIMI brand verification and no CAA certificate restriction (RFC 8659) — visual impersonation via lookalike domains and unrestricted certificate issuance remain open vectors

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.
Sources scanned (9)
  • https://reconfirm.com/
  • https://reconfirm.com/wp-content/plugins/google-analytics-for-wordpress/assets/js/frontend-gtag.min.js?ver=10.0.3
  • https://reconfirm.com/wp-content/plugins/elementor/assets/lib/font-awesome/js/v4-shims.min.js?ver=3.35.6
  • https://reconfirm.com/wp-content/plugins/weglot/dist/front-js.js?ver=5.4
  • https://reconfirm.com/wp-content/plugins/sticky-header-effects-for-elementor/assets/js/she-header.js?ver=2.1.8
  • https://reconfirm.com/wp-content/plugins/elementor/assets/js/webpack.runtime.min.js?ver=3.35.6
  • https://reconfirm.com/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.35.6
  • https://reconfirm.com/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.35.6
  • https://reconfirm.com/wp-content/plugins/th-widget-pack/js/themo-foot.js?ver=2.2.9
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 Hardened

No DNS server misconfigurations found on ns2.transip.eu — 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 Zone transfer denied (correct configuration)
Open Recursion Disabled Recursion disabled (correct configuration)
Nameserver Identity Hidden No nameserver identity information disclosed
Cache Snooping Protected Cache snooping not possible (correct configuration)

Tested nameservers: ns2.transip.eu, ns0.transip.net, ns1.transip.nl

Delegation Consistency 1 Issue

Delegation consistency: 1 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.

Findings:
  • Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

DS Key TagDS AlgorithmDNSKEY Key TagDNSKEY Algorithm
49064 13 49064 13

Glue Record Completeness Complete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
ns0.transip.net No N/A N/A OK
ns1.transip.nl No N/A N/A OK
ns2.transip.eu No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 86400s Drift: 0s

SOA Serial Consistency Consistent

ns0.transip.net: 2.026030902e+09
ns1.transip.nl: 2.026030902e+09
ns2.transip.eu: 2.026030902e+09
Nameserver Fleet Matrix Healthy

Analyzed 3 nameserver(s) for reconfirm.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
ns0.transip.net 195.135.195.195 2a01:7c8:dddd:195::195 AS20857 2026030902
ns1.transip.nl 195.8.195.195 2a01:7c8:7000:195::195 AS20857 2026030902
ns2.transip.eu 37.97.199.195 2a01:7c8:f:c1f::195 AS20857 2026030902
Unique ASNs
1
Unique Operators
0
Unique /24 Prefixes
3
Diversity Score
Fair

1 ASN(s), 3 /24 prefix(es) — consider adding diversity

DNSSEC Operations Deep Dive 2 Issues

DNSSEC operational notes: 2 item(s) to review — KSK/ZSK differentiation, RRSIG expiry windows, NSEC/NSEC3 analysis, and rollover readiness.

Findings:
  • NSEC3 uses a non-empty salt; RFC 9276 recommends empty salt for new deployments
  • Single KSK with no CDS/CDNSKEY automation — manual rollover required

DNSKEY Inventory 2 Keys

RoleKey TagAlgorithmKey Size
ZSK 44423 ECDSA P-256/SHA-256 256 bits
KSK 49064 ECDSA P-256/SHA-256 256 bits

RRSIG Signatures 0 Signatures

No RRSIG records found.

Denial of Existence NSEC3

Iterations: 0
Salt Length: 8 bytes
Hash Algorithm: 1 (SHA-1)

Rollover Readiness Not_ready

Multiple KSKs:
CDS Published:
CDNSKEY Published:
Automation: none
Mail Transport Security Beta Is mail transport encrypted and verified? Yes MTA-STS enforces TLS for all inbound mail delivery

All 1 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

Policy Assessment Primary
  • MTA-STS policy in enforce mode requires encrypted transport (RFC 8461)
  • TLS-RPT configured — domain monitors TLS delivery failures (RFC 8460)
  • Microsoft 365 enforces TLS 1.2+ with DANE (GA Oct 2024) and valid certificates
Telemetry
TLS-RPT configured — domain receives reports about TLS delivery failures from sending mail servers (RFC 8460)
Reporting to: mailto:f0c7af39@in.mailhardener.com
Live Probe Supplementary
MX Host STARTTLS TLS Version Cipher Certificate
reconfirm-com.mail.protection.outlook.com TLSv1.3 TLS_AES_256_GCM_SHA384 Valid
Expires: 2026-08-26 (169 days)
Issuer: DigiCert Inc
Multi-Vantage Probe Results
Unanimous: TLS verified 2 probes, 1 responded
France - EU observed
All servers support TLS
6.194545307s
US-East (Boston) skipped
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 1 unique ASN(s) across 2 IP address(es)

ASNNameCountry
AS34762 NL
IPv4 Mappings:
85.10.159.221 → AS34762 (85.10.156.0/22)
IPv6 Mappings:
2a01:7c8:f0:1131:0:1:ebd3:dc97 → AS34762 (2a01:7c8:f0::/46)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 1 service

1 SaaS service 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
Microsoft 365 MS=ms68388828
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 ECDSA P-256/SHA-256 Modern

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: ECDSA P-256/SHA-256 — MUST implement, recommended default (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):
49064 13 2 CC36ABE7E4760D66446430FAE12D7B28409EC86D41501B0F0E41163AF2BFB739

NS Delegation Verified

3 nameserver(s) configured

Nameservers: ns0.transip.net ns1.transip.nl ns2.transip.eu
Multi-Resolver Verification Recon: Consensus reached - 5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

85.10.159.221
Where the domain points for web traffic

AAAAIPv6 Address

2a01:7c8:f0:1131:0:1:ebd3:dc97
IPv6 ready

MXMail Servers

0 reconfirm-com.mail.protection.outlook.com.
Priority + mail server for email delivery
Microsoft 365

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (1 IPv4, 1 IPv6) Mail: 1 server Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 488 subdomains discovered
How did we find these?
CT logs unavailable 488 current 0 expired 1 CNAME 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)
a.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
academy.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
account.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
accounting.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
accounts.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ad.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
adfs.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
admin.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
admin1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
admin2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
alert.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
alerts.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
alpha.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
analytics.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ap-south.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ap.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
apac.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
api.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
api1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
api2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
api3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
apigw.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
apis.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
apm.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
app.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
app1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
app2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
appointments.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
apps.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
archive.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
archives.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
asia.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
assets.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
atom.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
auth.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
auth0.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
autoconfig.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
autodiscover.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
b.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
backup.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
backup1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
backup2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
beta.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
bi.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
bigdata.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
billing.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
bitbucket.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
blob.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
blog.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
booking.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
broker.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
bucket.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
build.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
builds.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
c.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ca.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cache.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cal.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
calendar.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
campaign.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
campaigns.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
careers.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cart.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
catalog.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cd.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cdn.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cdn1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cdn2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cdn3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cert.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
certs.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
chat.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
checkout.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ci.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
client.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
clients.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cloud.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cms.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cname.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
code.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
community.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
compliance.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
conference.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
config.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
configuration.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
confluence.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
connect.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
console.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
containers.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
content.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
corp.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
corporate.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
courses.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
cpanel.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
crl.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
crm.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
d.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
dashboard.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
data.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
data1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
data2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
database.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
datadog.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
db.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
db1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
db2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
dedicated.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
demo.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
deploy.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
deployment.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
dev.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
dev1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
dev2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
develop.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
developer.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
developers.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
devices.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
directory.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
discuss.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
discussions.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
dns.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
dns1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
dns2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
doc.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
docker.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
docs.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
documentation.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
download.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
downloads.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
drupal.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
e.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ecommerce.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
edge.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
edge1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
edge2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
education.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
elastic.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
elasticsearch.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
email.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
emea.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
endpoint.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
erp.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
es.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
etl.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
eu-west.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
eu.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
event.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
events.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
exchange.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ext.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
f.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
faq.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
feed.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
feedback.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
feeds.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
file.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
files.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
finance.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
firewall.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
forms.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
forum.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
forums.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ftp.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ftp1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ftp2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
fw.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
gateway.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
geo.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
gis.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
git.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
github.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
gitlab.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
go.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
grafana.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
graphql.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
gw.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
gw1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
gw2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
haproxy.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
health.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
healthcheck.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
help.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
helpdesk.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
hiring.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
host.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
hosting.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
hq.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
hr.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
hris.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
hub.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
id.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
identity.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
image.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
images.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
imap.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
img.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
int.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
internal.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
intranet.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
inventory.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
investor.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
investors.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
invoice.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ir.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
it.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
itsm.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
itsupport.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
jenkins.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
jira.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
jobs.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
k8s.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
kafka.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
kb.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
kibana.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
kong.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
kubernetes.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
lab.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
labs.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
lan.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
lb.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ldap.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
learn.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
learning.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
legal.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
link.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
links.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
live.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
lms.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
loadbalancer.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
location.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
log.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
login.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
logs.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
m.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mail.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mail1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mail2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mail3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
manage.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
management.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
manager.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
map.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
maps.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
marketing.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mdm.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
media.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
meet.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
meeting.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
memcached.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
metrics.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
microservices.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mobile.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mongo.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mongodb.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
monitor.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
monitoring.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mq.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mta-sts.reconfirm.com CT Log Current — 4 2026-03-09T15:29:19 Let's Encrypt
mta.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mx.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mx1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mx2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mx3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mx4.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mx5.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
my.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
myaccount.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
mysql.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
na.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
nagios.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
net.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
network.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
new2025.reconfirm.com CT Log Current — 2 2026-01-22T19:58:54 Let's Encrypt
news.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
nginx.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
node1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
node2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
node3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
notifications.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
notify.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ns.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ns1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ns2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ns3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ns4.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ns5.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ns6.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
o365.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
oauth.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
object.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ocsp.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
office.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
okta.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
order.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
orders.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
origin.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
origin1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
origin2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
outlook.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
owa.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
panel.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
partner.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
partners.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
pay.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
payment.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
payments.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
payroll.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
pbx.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
phone.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
photos.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
pki.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
plesk.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
policies.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
policy.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
pop.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
pop3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
portal.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
portal2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
postgres.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
pre.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
preprod.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
press.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
preview.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
primary.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
print.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
printer.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
privacy.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
private.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
product.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
products.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
profile.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
prometheus.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
promo.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
proxy.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
proxy1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
proxy2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
public.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
qa.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
queue.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
r.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ra.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
rabbitmq.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
rancher.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
realtime.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
recruit.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
redirect.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
redis.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
register.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
registry.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
relay.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
relay1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
releases.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
remote.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
repo.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
report.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
reporting.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
reports.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
repos.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
reservations.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
rest.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
rss.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
rt.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
s3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
sandbox.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
sandbox1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
sandbox2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
scan.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
scanner.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
schedule.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
scp.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
search.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
secondary.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
secrets.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
secure.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
server.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
server1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
server2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
server3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
service.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
servicedesk.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
services.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
sftp.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
share.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
shop.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
signin.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
signup.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
sip.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
slack.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
smtp.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
smtp1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
smtp2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
socket.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
solr.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
sql.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
srv.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
srv1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
srv2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ssh.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ssl.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
sso.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
stage.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
staging.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
static.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
static1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
static2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
statistics.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
stats.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
status.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
stg.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
storage.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
store.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
stream.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
streaming.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
support.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
support2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
survey.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
surveys.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
svc.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
svn.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
swift.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
talent.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
teams.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
techsupport.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
tel.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
telecom.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
terms.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
test.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
test1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
test2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
testing.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ticket.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
tickets.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
tls.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
tool.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
tools.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
trace.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
tracing.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
tracking.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
training.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
uat.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
upload.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
uploads.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
uptime.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
url.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
us-east.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
us-west.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
us.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
utility.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
varnish.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
vault.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
vendor.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
vendors.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
video.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
videos.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
voip.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
vpn.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
vpn1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
vpn2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
vpn3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
vps.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
waf.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
wan.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
warehouse.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
web.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
web1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
web2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
webex.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
webinar.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
webinars.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
webmail.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
websocket.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
whm.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
wiki.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
wordpress.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
work.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
worker.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
worker1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
worker2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
workspace.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
wp.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
ws.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
www.reconfirm.com DNS Current reconfirm.com 1 2025-03-26 Sectigo Limited
www1.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
www2.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
www3.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
xml.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
zabbix.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
zoom.reconfirm.com DNS Current — 1 2025-03-26 Sectigo Limited
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
85.10.159.221
85.10.159.221
AAAA Synchronized 1 / 1 records
2a01:7c8:f0:1131:0:1:ebd3:dc97
2a01:7c8:f0:1131:0:1:ebd3:dc97
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.reconfirm.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; sp=reject; rua=mailto:f0c7af39@in.mailhardener.com,mailto:f598f966@in.mailhardener.com; aspf=r; adkim=s; fo=1; ruf=mailto:dmarc@reconfirm.nl
v=DMARC1; p=reject; sp=reject; rua=mailto:f0c7af39@in.mailhardener.com,mailto:f598f966@in.mailhardener.com; aspf=r; adkim=s; fo=1; ruf=mailto:dmarc@reconfirm.nl
MTA-STS _mta-sts.reconfirm.com RFC 8461 §3 Synchronized 1 / 1 records
v=STSv1; id=20032023T211300;
v=STSv1; id=20032023T211300;
MX RFC 5321 Synchronized 1 / 1 records
0 reconfirm-com.mail.protection.outlook.com.
0 reconfirm-com.mail.protection.outlook.com.
NS RFC 1035 Synchronized 3 / 3 records
ns0.transip.net.
ns1.transip.nl.
ns2.transip.eu.
ns0.transip.net.
ns1.transip.nl.
ns2.transip.eu.
SOA RFC 1035 Synchronized 1 / 1 records
ns0.transip.net. hostmaster.transip.nl. 2026030902 86400 1800 2419200 300
ns0.transip.net. hostmaster.transip.nl. 2026030902 86400 1800 2419200 300
TLS-RPT _smtp._tls.reconfirm.com RFC 8460 §3 Synchronized 1 / 1 records
v=TLSRPTv1; rua=mailto:f0c7af39@in.mailhardener.com
v=TLSRPTv1; rua=mailto:f0c7af39@in.mailhardener.com
TXT RFC 7208 §4 Synchronized 2 / 2 records
MS=ms68388828
MS=ms68388828
v=spf1 include:spf.protection.outlook.com ~all
v=spf1 include:spf.protection.outlook.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.

efcaae3cfba0dee7ebf4986240c42d7a8b42bff0f53a66f643293660868c2b5a4c0117b415e7b7353d5ab0df14239b3d8e3eb1cf7e64b97be877bec7569088ec
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 10 Mar 2026, 15:20 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-reconfirm.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-reconfirm.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-reconfirm.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-reconfirm.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/7144/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 reconfirm.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 reconfirm.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer reconfirm.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer reconfirm.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer reconfirm.com NS
Query TXT records RFC 1035 
dig +noall +answer reconfirm.com TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

Test STARTTLS on primary MX (reconfirm-com.mail.protection.outlook.com) RFC 3207 
openssl s_client -starttls smtp -connect reconfirm-com.mail.protection.outlook.com:25 -servername reconfirm-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 85.10.159.221 (Team Cymru) 
dig +short 221.159.10.85.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 4846 runs
DKIM
Verified 4665 runs
DMARC
Verified 4830 runs
DANE/TLSA
Verified 4649 runs
DNSSEC
Verified 4827 runs
BIMI
Verified 4664 runs
MTA-STS
Verified 4667 runs
TLS-RPT
Verified 4669 runs
CAA
Verified 4661 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 reconfirm.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer reconfirm.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer reconfirm.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer reconfirm.com NS
Query TXT records (RFC 1035) 
dig +noall +answer reconfirm.com TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

Test STARTTLS on primary MX (reconfirm-com.mail.protection.outlook.com) (RFC 3207) 
openssl s_client -starttls smtp -connect reconfirm-com.mail.protection.outlook.com:25 -servername reconfirm-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

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

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