Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 22 Aug 2026, 22:39 UTC
Duration 61.7s
Version v26.51.0-135-g7ada422b6
Integrity 605dcbc35ea9d8d3187833a8337698b2759eb2416b8022b1a4813b4f72a8aa6f0ee8f3a3c94fbdc1927b5e2baea193c3e3013c9776710b10c83e5bb42afba077
Subject Domain
reissacupuncture.com

Engineer's DNS Intelligence Report

reissacupuncture.com Low Risk
22 Aug 2026, 22:39 UTC · 61.7s ·v26.51.0-135-g7ada422b6 · SHA-3-512: 605d✱✱✱✱ Verify ·Archived ·Cross-Referenced
Executive Topology Replay
Recon Mode Snapshot Re-analyze New Domain
Engineer workspace · evidence preserved

Read the verdict first. Descend only as far as the incident requires.

This report keeps the complete technical record while separating decision, interpretation, evidence, and raw reproduction into a stable disclosure gradient.

L0PostureL1InterpretationL2EvidenceL3Raw & reproduce
Hurry path
MX & Routing Subdomains DNSSEC What changed
KEYBOARD !1@2#3$4%5^6 jump to that section · esc back to the verdict
Sorted by severity — worst first
Email Spoofing
Protected
Brand Impersonation
Not Setup
DNS Tampering
Unconfirmed
Certificate Control
Configured
Monitoring
Partial
DANE
Unavailable on Provider
TRACE L0 · Brand Impersonation — Not Setup L1 · 04 · Brand & Trust · BIMI L3 · Reproduce commands
Not Configured
MTA-STS, TLS-RPT, BIMI
Monitoring
DNSSEC is configured but the chain of trust is unconfirmed — the AD flag was absent and RFC 4033 §5 cannot distinguish why
Unavailable on Provider
DANE
Configured
SPF, DMARC (reject), DKIM, CAA
Priority Actions Achievable posture: Hardened
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).

RFC 9495
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.

RFC 8460
Low Deploy MTA-STS

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

RFC 8461
Open Remediation Workspace — Copy-Paste Ready Records
Registrar (RDAP) OBSERVED LIVE
Launchpad.com Inc.
Where domain was purchased
Email Service Provider
Google Workspace
Strongly Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited
Footprint Google Workspace
01 Identity & policy · L1 Email Security Can this domain be impersonated by email? SPF DMARC DKIM MTA-STS TLS-RPT MX & Routing Protected
Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Gold

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.google.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 Gold

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

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; pct=100; sp=reject; adkim=r; aspf=r; fo=1; rf=afrf; ri=3600; rua=mailto:reports@reissacupuncture.com
Alignment: SPF relaxed DKIM relaxed sp=reject
No forensic reporting (ruf) tag — this is correct. The absence of ruf= is not a gap. 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 regardless. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification, confirming its deprecation. Omitting ruf= is the recommended modern practice. 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 Gold

Are outbound emails cryptographically signed? Yes — verified
Found 2048-bit

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

google._domainkey Google Workspace 2048-bit Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2mQqGswn1bndMKFc2GoX3uh0NpLSbEBIIOt1OVJ0t8j4ei+8hX4s+xfJaJtOHCycK2LiWH3s48ku+9bAdJFJN/rbaQIdNcAhDY0uCI0BnMdG71bOBxhcma/1oS9Mls5kT/wRrnfoH5YqNYrhHQCeJ/00ke59KwmVLWQKDWNryz6SF2jgmM5siNh1ahZV1nzzZssPgFDeWBjrnBwDFhsZucHEZrP2F5WQYKF6IE9ccBEcm5ET8EX3zypI8J8FpjWnOiGEvQSDtE+cqfzC/O8IoT0PASyb1uRp7Jh8LXhxbswaKW7PK5g1f5qicMUpP7vUCRc5KX9Wx6GIkdQfPJ+c7wIDAQAB
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 Gold

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 Gold

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

02 Chain of authority · L1 Domain Security Can DNS answers and certificate issuance be trusted? DANE / TLSA CAA Delegation DNSSEC Operations DNSSEC & NS Unconfirmed
DANE / TLSA Gold Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Available

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

DANE not deployable on Google Workspace

Google Workspace supports DANE for outbound mail verification but does not publish TLSA records for its MX hosts.

Recommended alternative: MTA-STS

Note: Google Workspace does validate DANE/TLSA when sending mail to DANE-enabled recipients (outbound DANE).

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 Google Workspace 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).

CAA RFC 8659 §4 Gold Success

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only Let's Encrypt can issue certificates

Authorized CAs: Let's Encrypt
0 issue "letsencrypt.org"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
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
7826 13 7826 13

Glue Record Completeness Complete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
ns1.dnsbycomodo.net No N/A N/A OK
ns2.dnsbycomodo.net No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 86400s Drift: 0s

SOA Serial Consistency Consistent

ns1.dnsbycomodo.net: 2.026082201e+09
ns2.dnsbycomodo.net: 2.026082201e+09
DNSSEC Operations Deep Dive 1 Issue

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

Findings:
  • Single KSK with no CDS/CDNSKEY automation — manual rollover required

DNSKEY Inventory 2 Keys

RoleKey TagAlgorithmKey Size
ZSK 40025 ECDSA P-256/SHA-256 256 bits
KSK 7826 ECDSA P-256/SHA-256 256 bits

RRSIG Signatures 0 Signatures

No RRSIG records found.

Denial of Existence none

No NSEC or NSEC3 records detected.

Rollover Readiness Not_ready

Multiple KSKs:
CDS Published:
CDNSKEY Published:
Automation: none
Domain Security Methodology Can DNS responses be tampered with in transit? Unknown DNSSEC could not be confirmed — re-run to verify. This is not evidence the zone is unsigned (RFC 4035).

DNSSEC RFC 4033 §2 Gold Unconfirmed ECDSA P-256/SHA-256 Modern

DNSSEC configured (DNSKEY + DS records present) but validating resolvers disagree on the chain — not uniformly confirmed.

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.
DNSSEC is configured (DNSKEY + DS records present) but the chain of trust is not uniformly confirmed — the AD flag was absent or validating resolvers disagreed (RFC 4033 §5 cannot distinguish an insecure delegation from an indeterminate result from the AD-absent signal alone).
DS Record (at registrar):
7826 13 2 8F5FABDBD4EC930BD174031BC755B56356FABF309850C1EA38F008C6BBE29522

NS Delegation Verified

2 nameserver(s) configured

Nameservers: ns1.dnsbycomodo.net ns2.dnsbycomodo.net
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (3 differences found)
Resolver Differences:
MX: DNS4EU returned different results: []
NS: DNS4EU returned different results: []
TXT: DNS4EU returned different results: []
This may indicate DNS propagation in progress or geo-based DNS routing.
03 Delivery path · L1 Transport Security Will mail transport resist downgrade and interception? STARTTLS MTA-STS policy TLS-RPT
Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

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

Policy Assessment Primary
  • Google Workspace enforces TLS 1.2+ with valid certificates on all inbound/outbound mail
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
MX Host STARTTLS TLS Version Cipher Key Exchange Certificate
smtp.google.com TLSv1.3 TLS_AES_128_GCM_SHA256 N/A Valid
Expires: 2026-10-28 (66 days)
Issuer: Google Trust Services
Multi-Vantage Probe Results
Unanimous: TLS verified 3 probes, 1 responded
EU (Paris) observed
All servers support TLS
6.222868442s
APAC (Singapore) skipped
US-East (Virginia) skipped
What Is Measured: Our probe’s TLS 1.3 handshake offers the hybrid post-quantum group X25519MLKEM768 (X25519 combined with ML-KEM-768). The Key Exchange column reports the group each mail server actually negotiated — direct, observed evidence of its post-quantum readiness toward a hybrid-capable client.
Quantum-Safe Hybrid: The session key agreement combines classical X25519 with ML-KEM-768, standardized in FIPS 203 (final, August 2024). This protects the key exchange against “harvest now, decrypt later” collection by a future quantum adversary.
Classical: The server completed the handshake without selecting the offered hybrid group. This is not a deviation — no RFC currently requires post-quantum key exchange. The X25519MLKEM768 group is defined in draft-ietf-tls-ecdhe-mlkem (Standards Track draft, not yet an RFC); the hybrid approach is described in draft-ietf-tls-hybrid-design (IESG-approved Informational). Servers supporting only other hybrid groups also read as Classical here.
Transition Outlook: NIST’s draft transition guidance (NIST IR 8547) projects quantum-vulnerable algorithms being deprecated after 2030 and disallowed after 2035. Hybrid key exchange requires TLS 1.3. This finding is informational and does not affect this domain’s grade.
04 Human-visible identity · L1 Brand & Trust Can this brand be convincingly faked? BIMI & VMC CAA · see Domain Security Not Setup
Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

BIMI BIMI Spec Gold Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

05 Ownership & attack surface · L1 Infrastructure Intelligence Who operates this domain, and what is exposed? Registrar / RDAP security.txt AI Surface Subdomains
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116

Could not fetch security.txt

Fetch error: SSL error
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 View 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 (1)
  • http://reissacupuncture.com/
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 ns1.dnsbycomodo.net — 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: ns1.dnsbycomodo.net, ns2.dnsbycomodo.net

Nameserver Fleet Matrix 1 Issue

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

Findings:
  • Low nameserver diversity — all nameservers in a single ASN/prefix
Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial Anycast Node
ns1.dnsbycomodo.net 199.167.66.21 2610:1c8:b001::1 AS23393 2026082201 21ms
ns2.dnsbycomodo.net 199.167.66.22 2610:1c8:b002::1 AS23393 2026082201 21ms
Unique ASNs
1
Unique Operators
0
Unique /24 Prefixes
1
Diversity Score
Poor

All 2 nameservers in a single ASN and /24 prefix — single point of failure risk

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

IPv4 Mappings:
108.167.161.79 → AS ()

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success

No SaaS verification records detected

Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.

Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

108.167.161.79
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

1 smtp.google.com.
Priority + mail server for email delivery
Google Workspace

SRVServices

_autodiscover._tcp: 0 0 443 cpanelemaildiscovery.cpanel.net.
SIP, XMPP, or other service endpoints
Web: Reachable (1 IPv4, 0 IPv6) Mail: 1 server Services: 1 endpoint
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 321 subdomains discovered
How did we find these?
Certificate Transparency Logs Unavailable The results below are from DNS probing only and may be significantly incomplete. CT logs typically reveal hundreds or thousands of additional subdomains via certificate issuance history (RFC 6962). The CT log server was temporarily unavailable and is in a cooldown period.
Re-Analyze to Retry CT Lookup
CT logs unavailable 321 current 0 expired 2 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)
a.reissacupuncture.com DNS Current — — — —
account.reissacupuncture.com DNS Current — — — —
accounts.reissacupuncture.com DNS Current — — — —
ad.reissacupuncture.com DNS Current — — — —
admin.reissacupuncture.com DNS Current — — — —
admin1.reissacupuncture.com DNS Current — — — —
alert.reissacupuncture.com DNS Current — — — —
alerts.reissacupuncture.com DNS Current — — — —
alpha.reissacupuncture.com DNS Current — — — —
analytics.reissacupuncture.com DNS Current — — — —
apac.reissacupuncture.com DNS Current — — — —
api1.reissacupuncture.com DNS Current — — — —
api2.reissacupuncture.com DNS Current — — — —
apis.reissacupuncture.com DNS Current — — — —
apm.reissacupuncture.com DNS Current — — — —
app1.reissacupuncture.com DNS Current — — — —
app2.reissacupuncture.com DNS Current — — — —
apps.reissacupuncture.com DNS Current — — — —
archive.reissacupuncture.com DNS Current — — — —
archives.reissacupuncture.com DNS Current — — — —
atom.reissacupuncture.com DNS Current — — — —
auth.reissacupuncture.com DNS Current — — — —
autodiscover.reissacupuncture.com CT Log Current — — — —
b.reissacupuncture.com DNS Current — — — —
backup.reissacupuncture.com DNS Current — — — —
bi.reissacupuncture.com DNS Current — — — —
bigdata.reissacupuncture.com DNS Current — — — —
billing.reissacupuncture.com DNS Current — — — —
bitbucket.reissacupuncture.com DNS Current — — — —
blog.reissacupuncture.com DNS Current — — — —
bucket.reissacupuncture.com DNS Current — — — —
builds.reissacupuncture.com DNS Current — — — —
c.reissacupuncture.com DNS Current — — — —
catalog.reissacupuncture.com DNS Current — — — —
cdn.reissacupuncture.com DNS Current — — — —
cdn2.reissacupuncture.com DNS Current — — — —
cdn3.reissacupuncture.com DNS Current — — — —
cert.reissacupuncture.com DNS Current — — — —
checkout.reissacupuncture.com DNS Current — — — —
ci.reissacupuncture.com DNS Current — — — —
cloud.reissacupuncture.com DNS Current — — — —
code.reissacupuncture.com DNS Current — — — —
config.reissacupuncture.com DNS Current — — — —
configuration.reissacupuncture.com DNS Current — — — —
confluence.reissacupuncture.com DNS Current — — — —
connect.reissacupuncture.com DNS Current — — — —
containers.reissacupuncture.com DNS Current — — — —
content.reissacupuncture.com DNS Current — — — —
corp.reissacupuncture.com DNS Current — — — —
corporate.reissacupuncture.com DNS Current — — — —
courses.reissacupuncture.com DNS Current — — — —
cpanel.reissacupuncture.com DNS Current — — — —
cpcalendars.reissacupuncture.com CT Log Current — — — —
cpcontacts.reissacupuncture.com CT Log Current — — — —
d.reissacupuncture.com DNS Current — — — —
data2.reissacupuncture.com DNS Current — — — —
datadog.reissacupuncture.com DNS Current — — — —
db.reissacupuncture.com DNS Current — — — —
db1.reissacupuncture.com DNS Current — — — —
db2.reissacupuncture.com DNS Current — — — —
dedicated.reissacupuncture.com DNS Current — — — —
deploy.reissacupuncture.com DNS Current — — — —
deployment.reissacupuncture.com DNS Current — — — —
dev.reissacupuncture.com DNS Current — — — —
dev1.reissacupuncture.com DNS Current — — — —
developers.reissacupuncture.com DNS Current — — — —
devices.reissacupuncture.com DNS Current — — — —
discuss.reissacupuncture.com DNS Current — — — —
dns.reissacupuncture.com DNS Current — — — —
dns1.reissacupuncture.com DNS Current — — — —
dns2.reissacupuncture.com DNS Current — — — —
doc.reissacupuncture.com DNS Current — — — —
docker.reissacupuncture.com DNS Current — — — —
docs.reissacupuncture.com DNS Current — — — —
documentation.reissacupuncture.com DNS Current — — — —
drupal.reissacupuncture.com DNS Current — — — —
e.reissacupuncture.com DNS Current — — — —
edge.reissacupuncture.com DNS Current — — — —
edge1.reissacupuncture.com DNS Current — — — —
elastic.reissacupuncture.com DNS Current — — — —
email.reissacupuncture.com DNS Current — — — —
emea.reissacupuncture.com DNS Current — — — —
es.reissacupuncture.com DNS Current — — — —
etl.reissacupuncture.com DNS Current — — — —
event.reissacupuncture.com DNS Current — — — —
events.reissacupuncture.com DNS Current — — — —
exchange.reissacupuncture.com DNS Current — — — —
f.reissacupuncture.com DNS Current — — — —
feed.reissacupuncture.com DNS Current — — — —
feedback.reissacupuncture.com DNS Current — — — —
feeds.reissacupuncture.com DNS Current — — — —
file.reissacupuncture.com DNS Current — — — —
finance.reissacupuncture.com DNS Current — — — —
firewall.reissacupuncture.com DNS Current — — — —
forms.reissacupuncture.com DNS Current — — — —
forum.reissacupuncture.com DNS Current — — — —
ftp.reissacupuncture.com DNS Current — — — —
gateway.reissacupuncture.com DNS Current — — — —
geo.reissacupuncture.com DNS Current — — — —
github.reissacupuncture.com DNS Current — — — —
gitlab.reissacupuncture.com DNS Current — — — —
grafana.reissacupuncture.com DNS Current — — — —
graphql.reissacupuncture.com DNS Current — — — —
gw1.reissacupuncture.com DNS Current — — — —
haproxy.reissacupuncture.com DNS Current — — — —
health.reissacupuncture.com DNS Current — — — —
helpdesk.reissacupuncture.com DNS Current — — — —
hiring.reissacupuncture.com DNS Current — — — —
host.reissacupuncture.com DNS Current — — — —
hosting.reissacupuncture.com DNS Current — — — —
hr.reissacupuncture.com DNS Current — — — —
hub.reissacupuncture.com DNS Current — — — —
identity.reissacupuncture.com DNS Current — — — —
image.reissacupuncture.com DNS Current — — — —
images.reissacupuncture.com DNS Current — — — —
img.reissacupuncture.com DNS Current — — — —
int.reissacupuncture.com DNS Current — — — —
internal.reissacupuncture.com DNS Current — — — —
intranet.reissacupuncture.com DNS Current — — — —
inventory.reissacupuncture.com DNS Current — — — —
investor.reissacupuncture.com DNS Current — — — —
it.reissacupuncture.com DNS Current — — — —
jenkins.reissacupuncture.com DNS Current — — — —
kafka.reissacupuncture.com DNS Current — — — —
kong.reissacupuncture.com DNS Current — — — —
kubernetes.reissacupuncture.com DNS Current — — — —
lab.reissacupuncture.com DNS Current — — — —
labs.reissacupuncture.com DNS Current — — — —
lan.reissacupuncture.com DNS Current — — — —
learning.reissacupuncture.com DNS Current — — — —
legal.reissacupuncture.com DNS Current — — — —
link.reissacupuncture.com DNS Current — — — —
live.reissacupuncture.com DNS Current — — — —
lms.reissacupuncture.com DNS Current — — — —
loadbalancer.reissacupuncture.com DNS Current — — — —
log.reissacupuncture.com DNS Current — — — —
login.reissacupuncture.com DNS Current — — — —
logs.reissacupuncture.com DNS Current — — — —
lookup.reissacupuncture.com DNS Current — — — —
mail.reissacupuncture.com DNS Current — — — —
mail1.reissacupuncture.com DNS Current — — — —
mail2.reissacupuncture.com DNS Current — — — —
mail3.reissacupuncture.com DNS Current — — — —
mailgw.reissacupuncture.com DNS Current — — — —
mailhost.reissacupuncture.com DNS Current — — — —
mailserver.reissacupuncture.com DNS Current — — — —
manage.reissacupuncture.com DNS Current — — — —
management.reissacupuncture.com DNS Current — — — —
manager.reissacupuncture.com DNS Current — — — —
map.reissacupuncture.com DNS Current — — — —
marketing.reissacupuncture.com DNS Current — — — —
media.reissacupuncture.com DNS Current — — — —
meet.reissacupuncture.com DNS Current — — — —
memcached.reissacupuncture.com DNS Current — — — —
mobile.reissacupuncture.com DNS Current — — — —
mongodb.reissacupuncture.com DNS Current — — — —
monitor.reissacupuncture.com DNS Current — — — —
monitoring.reissacupuncture.com DNS Current — — — —
mq.reissacupuncture.com DNS Current — — — —
mx.reissacupuncture.com DNS Current — — — —
mx3.reissacupuncture.com DNS Current — — — —
mx4.reissacupuncture.com DNS Current — — — —
mxtoolbox.reissacupuncture.com DNS Current — — — —
myaccount.reissacupuncture.com DNS Current — — — —
net.reissacupuncture.com DNS Current — — — —
netadmin.reissacupuncture.com DNS Current — — — —
nettool.reissacupuncture.com DNS Current — — — —
node1.reissacupuncture.com DNS Current — — — —
node3.reissacupuncture.com DNS Current — — — —
notify.reissacupuncture.com DNS Current — — — —
ns.reissacupuncture.com DNS Current — — — —
ns1.reissacupuncture.com DNS Current — — — —
ns2.reissacupuncture.com DNS Current — — — —
ns3.reissacupuncture.com DNS Current — — — —
ns4.reissacupuncture.com DNS Current — — — —
ns5.reissacupuncture.com DNS Current — — — —
ns6.reissacupuncture.com DNS Current — — — —
o365.reissacupuncture.com DNS Current — — — —
okta.reissacupuncture.com DNS Current — — — —
order.reissacupuncture.com DNS Current — — — —
orders.reissacupuncture.com DNS Current — — — —
origin.reissacupuncture.com DNS Current — — — —
outlook.reissacupuncture.com DNS Current — — — —
panel.reissacupuncture.com DNS Current — — — —
partner.reissacupuncture.com DNS Current — — — —
partners.reissacupuncture.com DNS Current — — — —
pay.reissacupuncture.com DNS Current — — — —
payment.reissacupuncture.com DNS Current — — — —
payments.reissacupuncture.com DNS Current — — — —
phone.reissacupuncture.com DNS Current — — — —
photos.reissacupuncture.com DNS Current — — — —
pingdom.reissacupuncture.com DNS Current — — — —
pki.reissacupuncture.com DNS Current — — — —
plesk.reissacupuncture.com DNS Current — — — —
policies.reissacupuncture.com DNS Current — — — —
policy.reissacupuncture.com DNS Current — — — —
pop.reissacupuncture.com DNS Current — — — —
portal.reissacupuncture.com DNS Current — — — —
portal2.reissacupuncture.com DNS Current — — — —
pre.reissacupuncture.com DNS Current — — — —
preprod.reissacupuncture.com DNS Current — — — —
press.reissacupuncture.com DNS Current — — — —
preview.reissacupuncture.com DNS Current — — — —
primary.reissacupuncture.com DNS Current — — — —
print.reissacupuncture.com DNS Current — — — —
privacy.reissacupuncture.com DNS Current — — — —
private.reissacupuncture.com DNS Current — — — —
product.reissacupuncture.com DNS Current — — — —
profile.reissacupuncture.com DNS Current — — — —
promo.reissacupuncture.com DNS Current — — — —
proxy.reissacupuncture.com DNS Current — — — —
public.reissacupuncture.com DNS Current — — — —
ra.reissacupuncture.com DNS Current — — — —
rancher.reissacupuncture.com DNS Current — — — —
realtime.reissacupuncture.com DNS Current — — — —
recruit.reissacupuncture.com DNS Current — — — —
redirect.reissacupuncture.com DNS Current — — — —
redis.reissacupuncture.com DNS Current — — — —
register.reissacupuncture.com DNS Current — — — —
registry.reissacupuncture.com DNS Current — — — —
relay.reissacupuncture.com DNS Current — — — —
relay1.reissacupuncture.com DNS Current — — — —
releases.reissacupuncture.com DNS Current — — — —
remote.reissacupuncture.com DNS Current — — — —
repo.reissacupuncture.com DNS Current — — — —
reporting.reissacupuncture.com DNS Current — — — —
reports.reissacupuncture.com DNS Current — — — —
repos.reissacupuncture.com DNS Current — — — —
reservations.reissacupuncture.com DNS Current — — — —
rss.reissacupuncture.com DNS Current — — — —
rt.reissacupuncture.com DNS Current — — — —
s3.reissacupuncture.com DNS Current — — — —
sandbox.reissacupuncture.com DNS Current — — — —
scanner.reissacupuncture.com DNS Current — — — —
schedule.reissacupuncture.com DNS Current — — — —
search.reissacupuncture.com DNS Current — — — —
secure.reissacupuncture.com DNS Current — — — —
server3.reissacupuncture.com DNS Current — — — —
service.reissacupuncture.com DNS Current — — — —
servicedesk.reissacupuncture.com DNS Current — — — —
services.reissacupuncture.com DNS Current — — — —
sftp.reissacupuncture.com DNS Current — — — —
shop.reissacupuncture.com DNS Current — — — —
sip.reissacupuncture.com DNS Current — — — —
slack.reissacupuncture.com DNS Current — — — —
smtp2.reissacupuncture.com DNS Current — — — —
socket.reissacupuncture.com DNS Current — — — —
solr.reissacupuncture.com DNS Current — — — —
srv.reissacupuncture.com DNS Current — — — —
srv2.reissacupuncture.com DNS Current — — — —
ssl.reissacupuncture.com DNS Current — — — —
sso.reissacupuncture.com DNS Current — — — —
static.reissacupuncture.com DNS Current — — — —
statistics.reissacupuncture.com DNS Current — — — —
stats.reissacupuncture.com DNS Current — — — —
status.reissacupuncture.com DNS Current — — — —
statuspage.reissacupuncture.com DNS Current — — — —
storage.reissacupuncture.com DNS Current — — — —
store.reissacupuncture.com DNS Current — — — —
streaming.reissacupuncture.com DNS Current — — — —
support.reissacupuncture.com DNS Current — — — —
svc.reissacupuncture.com DNS Current — — — —
svn.reissacupuncture.com DNS Current — — — —
syslog.reissacupuncture.com DNS Current — — — —
talent.reissacupuncture.com DNS Current — — — —
teams.reissacupuncture.com DNS Current — — — —
techsupport.reissacupuncture.com DNS Current — — — —
telecom.reissacupuncture.com DNS Current — — — —
terms.reissacupuncture.com DNS Current — — — —
test.reissacupuncture.com DNS Current — — — —
ticket.reissacupuncture.com DNS Current — — — —
tls.reissacupuncture.com DNS Current — — — —
tool.reissacupuncture.com DNS Current — — — —
tracing.reissacupuncture.com DNS Current — — — —
tracking.reissacupuncture.com DNS Current — — — —
training.reissacupuncture.com DNS Current — — — —
uat.reissacupuncture.com DNS Current — — — —
upload.reissacupuncture.com DNS Current — — — —
uploads.reissacupuncture.com DNS Current — — — —
uptime.reissacupuncture.com DNS Current — — — —
us-east.reissacupuncture.com DNS Current — — — —
us-west.reissacupuncture.com DNS Current — — — —
us.reissacupuncture.com DNS Current — — — —
utility.reissacupuncture.com DNS Current — — — —
vault.reissacupuncture.com DNS Current — — — —
vendor.reissacupuncture.com DNS Current — — — —
vendors.reissacupuncture.com DNS Current — — — —
video.reissacupuncture.com DNS Current — — — —
voip.reissacupuncture.com DNS Current — — — —
vpn1.reissacupuncture.com DNS Current — — — —
vpn2.reissacupuncture.com DNS Current — — — —
vpn3.reissacupuncture.com DNS Current — — — —
waf.reissacupuncture.com DNS Current — — — —
wan.reissacupuncture.com DNS Current — — — —
warehouse.reissacupuncture.com DNS Current — — — —
web.reissacupuncture.com DNS Current — — — —
web1.reissacupuncture.com DNS Current — — — —
web2.reissacupuncture.com DNS Current — — — —
webdisk.reissacupuncture.com CT Log Current — — — —
webex.reissacupuncture.com DNS Current — — — —
webhost.reissacupuncture.com DNS Current — — — —
webinar.reissacupuncture.com DNS Current — — — —
webinars.reissacupuncture.com DNS Current — — — —
webmail.reissacupuncture.com DNS Current reissacupuncture.com — — —
webserver.reissacupuncture.com DNS Current — — — —
webtool.reissacupuncture.com DNS Current — — — —
webtools.reissacupuncture.com DNS Current — — — —
whm.reissacupuncture.com DNS Current — — — —
whois.reissacupuncture.com DNS Current — — — —
wordpress.reissacupuncture.com DNS Current — — — —
work.reissacupuncture.com DNS Current — — — —
worker.reissacupuncture.com DNS Current — — — —
worker1.reissacupuncture.com DNS Current — — — —
worker2.reissacupuncture.com DNS Current — — — —
workspace.reissacupuncture.com DNS Current — — — —
wp.reissacupuncture.com DNS Current — — — —
www.reissacupuncture.com DNS Current reissacupuncture.com — — —
www1.reissacupuncture.com DNS Current — — — —
www2.reissacupuncture.com DNS Current — — — —
zabbix.reissacupuncture.com DNS Current — — — —
zoom.reissacupuncture.com DNS Current — — — —
Export Recon (CSV)
Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
06 Raw records & reproducibility · L2–L3 Evidence & Verification Can another engineer reproduce every material claim? Analysis Confidence Intelligence Currency What changed Raw record diff Integrity seal Reproduce
Strong resolver agreement, fresh and complete data, and proven measurement tooling support high confidence in this analysis.
Accuracy 76% Currency 78/100 Maturity gold
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Adequate TTL Relevance Excellent
ICuAE Details
DNS data is mostly current with minor gaps — good intelligence currency
Primary NS ns1.dnsbycomodo.net
Serial 2026082201
Admin admin.dns.com
Provider Unknown
Timer Value RFC 1912 Range
Refresh10800s1,200–43,200s (20 min – 12 hrs)
Retry864000sFraction of Refresh
Expire7200s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)7200s300–86,400s (5 min – 1 day)
Expire: SOA Expire is 2 hours (7200s). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). If the primary nameserver becomes unreachable, secondary nameservers will stop serving this zone after only 2 hours (7200s).
RFC 1912 §2.2
Expire vs Refresh+Retry: If Expire is not greater than Refresh + Retry, secondary nameservers may stop serving the zone before they've had a chance to retry the primary.
RFC 1912 §2.2
Suggested Scanner Configuration Medium Confidence
Based on 9 historical scans of this domain
Parameter Current Suggested Severity Rationale
resolver_set 5 resolvers, 63% agreement Add additional resolvers or replace low-agreement ones medium Resolver agreement rate is 62.9%, below the 70% threshold. Low agreement indicates potential DNS propagation issues or resolver-specific caching behavior. Adding diverse resolvers improves measurement confidence.
NIST SP 800-53 SI-7
timeout_seconds 5s 8s low Average scan duration is 60.5s, 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.
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 1 / 0 records
108.167.161.79
—
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 Synchronized 1 / 1 records
0 issue "letsencrypt.org"
0 issue "letsencrypt.org"
DMARC _dmarc.reissacupuncture.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; pct=100; sp=reject; adkim=r; aspf=r; fo=1; rf=afrf; ri=3600; rua=mailto:reports@reissacupuncture.com
v=DMARC1; p=reject; pct=100; sp=reject; adkim=r; aspf=r; fo=1; rf=afrf; ri=3600; rua=mailto:reports@reissacupuncture.com
MX RFC 5321 Synchronized 1 / 1 records
1 smtp.google.com.
1 smtp.google.com.
NS RFC 1035 Synchronized 2 / 2 records
ns1.dnsbycomodo.net.
ns1.dnsbycomodo.net.
ns2.dnsbycomodo.net.
ns2.dnsbycomodo.net.
SOA RFC 1035 Synchronized 1 / 1 records
ns1.dnsbycomodo.net. admin.dns.com. 2026082201 10800 864000 7200 7200
ns1.dnsbycomodo.net. admin.dns.com. 2026082201 10800 864000 7200 7200
TXT RFC 7208 §4 Synchronized 1 / 1 records
v=spf1 include:_spf.google.com ~all
v=spf1 include:_spf.google.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.

605dcbc35ea9d8d3187833a8337698b2759eb2416b8022b1a4813b4f72a8aa6f0ee8f3a3c94fbdc1927b5e2baea193c3e3013c9776710b10c83e5bb42afba077
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 22 Aug 2026, 22:39 UTC.
Internet Archive — Permanent Record Wayback Machine Can this analysis be independently verified? Archived

This analysis has been automatically submitted to the Internet Archive's Wayback Machine, creating a tamper-evident, third-party-hosted snapshot of the DNS security posture at analysis time. This archived copy is independent of DNS Tool — it provides an independently verifiable record of the analysis at this point in time. Combined with the SHA-3-512 integrity hash, this creates a verifiable chain of evidence for domain security state.

View Archived Snapshot
Snapshot preserved at https://web.archive.org/web/20260822223920/https://dnstool.it-help.tech/analysis/18478/view/E
Download Raw Intelligence Download Checksum (.sha3) Cross-Reference Verification

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

Email Authentication

Check SPF record RFC 7208 
dig +short reissacupuncture.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.reissacupuncture.com TXT
Check DKIM key for selector 'google' RFC 6376 
dig +short google._domainkey.reissacupuncture.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 108.167.161.79 (Team Cymru) 
dig +short 79.161.167.108.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 gold · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Gold 15673 runs
DKIM
Gold 15463 runs
DMARC
Gold 15654 runs
DANE/TLSA
Gold 15445 runs
DNSSEC
Gold 15632 runs
BIMI
Gold 15460 runs
MTA-STS
Gold 15481 runs
TLS-RPT
Gold 15496 runs
CAA
Gold 15493 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 reissacupuncture.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer reissacupuncture.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer reissacupuncture.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer reissacupuncture.com NS
Query TXT records (RFC 1035) 
dig +noall +answer reissacupuncture.com TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 108.167.161.79 (Team Cymru) 
dig +short 79.161.167.108.origin.asn.cymru.com TXT

0s

Running Real-Time Scan Telemetry

Most scans complete in less than one minute. Some may take longer.

Markers represent known resolver locations. Anycast routing selects the nearest node — exact routing is internal to each provider.

Pipeline nodes reflect live data as each analysis phase completes.

Telemetry Log 0 polls