Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 14 Feb 2026, 05:52 UTC
Duration 5.5s
Version v26.12.28
Integrity fc671cc6b10d59e79ec16be44ec62bcf7f507989476805d9c546456ae94025130cb65a217a3761672ecc187749d076603065fb08ed8be54b2cfa2dbe58bb206e
Subject Domain
mobilecommercepress.com

Engineer's DNS Intelligence Report

mobilecommercepress.com
14 Feb 2026, 05:52 UTC · 5.5s ·v26.12.28 · SHA-3-512: fc67✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint 1 SaaS Service
DNS Security & Trust Posture
Risk Level: High Risk
1 protocols configured, 5 not configured Why we go beyond letter grades
1 action required 1 recommendation 1 monitoring
Suggested Scanner Configuration Medium Confidence
Based on 7 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 36.4s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures.
RFC 8767
Suggestions require explicit approval before applying. No automatic changes will be made.
Email Spoofing
Partial
Brand Impersonation
Not Setup
DNS Tampering
Enterprise
Certificate Control
Open
Action Required
No DMARC record
Recommended
DKIM not discoverable via common selectors — may be configured with custom or rotating selectors (RFC 6376 §3.6.2.1)
Monitoring
DKIM (inconclusive)
Configured
SPF (~all)
Not Configured
DMARC, MTA-STS, TLS-RPT, CAA, DNSSEC
Priority Actions 7 total Achievable posture: Medium Risk
Critical Publish DMARC policy

DMARC (Domain-based Message Authentication, Reporting & Conformance) tells receivers how to handle messages that fail SPF/DKIM checks. Without DMARC, failed authentication checks are ignored. Start with p=none and rua reporting to monitor, then escalate to p=quarantine and p=reject.

_dmarc.mobilecommercepress.com TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@mobilecommercepress.com"
RFC 7489 §6.3
Medium Deploy MTA-STS policy

Publish an MTA-STS DNS record and host a policy file at https://mta-sts.mobilecommercepress.com/.well-known/mta-sts.txt. This tells senders to require TLS when delivering mail to your domain.

_mta-sts.mobilecommercepress.com TXT "v=STSv1; id=20240101"
RFC 8461 §3
Low Upgrade SPF to hard fail (-all)

Your SPF record uses ~all (softfail) and no DKIM signing was detected. Without DKIM, SPF is your only line of defense — upgrading to -all (hardfail) instructs receivers to reject unauthorized senders outright. Verify all legitimate sending sources are included before switching. If you configure DKIM, ~all becomes the industry-standard best practice because DMARC evaluates both SPF and DKIM alignment (RFC 7489 §10.1).

mobilecommercepress.com TXT "v=spf1 include:relay.mailchannels.net include:relay.mailchannels.net include:bluehost.com -all"
RFC 7208 §5
Low Verify DKIM configuration

DKIM selectors were not discoverable via common selector names. This does not confirm DKIM is absent — your provider may use custom or rotating selectors that cannot be enumerated through DNS (RFC 6376 §3.6.2.1). Check your email provider's DKIM settings to confirm signing is enabled.

selector1._domainkey.mobilecommercepress.com TXT "v=DKIM1; k=rsa; p=<public_key>"
RFC 6376 §3.6.2.1
Low Add CAA records

Publish CAA DNS records to restrict which Certificate Authorities can issue TLS certificates for your domain. Specify your preferred CA (e.g., letsencrypt.org, digicert.com). CAA is advisory — CAs must check it before issuing, but absence means any CA can issue.

mobilecommercepress.com CAA 0 issue "letsencrypt.org"
RFC 8659 §4
Low Configure TLS-RPT reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain. Helps diagnose MTA-STS and STARTTLS issues.

_smtp._tls.mobilecommercepress.com TXT "v=TLSRPTv1; rua=mailto:tls-reports@mobilecommercepress.com"
RFC 8460 §3
Low Enable DNSSEC

DNSSEC (DNS Security Extensions) cryptographically signs DNS responses, preventing attackers from forging DNS answers. Contact your DNS hosting provider to enable DNSSEC signing.

RFC 4033 §2
Registrar (RDAP) OBSERVED LIVE
Domain.com - Network Solutions, LLC
Where domain was purchased
Email Service Provider OBSERVED
Unknown
Email: Enabled
Web Hosting INFERRED
Cloudflare (CDN)
Where website is hosted
DNS Hosting OBSERVED
Cloudflare Enterprise
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? Yes
Verdict: SPF is configured but without DMARC, receiving servers may still accept spoofed messages.

SPF Record RFC 7208 §4 Verified

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

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

v=spf1 ip4:72.52.246.3 +a +mx +ip4:129.121.178.52 +include:relay.mailchannels.net +include:relay.mailchannels.net +include:bluehost.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.
Upgrade SPF to hard fail (-all):
mobilecommercepress.com TXT "v=spf1 include:relay.mailchannels.net include:relay.mailchannels.net include:bluehost.com -all"

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? No policy published
Warning

No DMARC record found

Publish DMARC policy:
_dmarc.mobilecommercepress.com TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@mobilecommercepress.com"
RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
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? Not discoverable
Not Discoverable

DKIM not discoverable via common selectors (large providers use rotating selectors)

RFC 6376 (Provider-Managed) — DKIM signing managed by the detected mail provider per RFC 6376.
Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Verified

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No MTA-STS record found

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

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

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

No DANE/TLSA records found (checked 1 MX host)

DANE (RFC 7672) binds TLS certificates to DNSSEC-signed DNS records, protecting email transport against man-in-the-middle attacks and rogue CAs. It is the primary transport security standard — MTA-STS (RFC 8461) was created as the alternative for domains that cannot deploy DNSSEC. Over 1 million domains use DANE globally, including Microsoft Exchange Online, Proton Mail, and Fastmail. Best practice: deploy both for defense in depth.
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. Mail transport relies on opportunistic TLS without policy enforcement, leaving it vulnerable to downgrade attacks. Deploy DANE (RFC 7672) with DNSSEC for the strongest protection, or MTA-STS (RFC 8461) if DNSSEC is not feasible.

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?
Verdict: No brand protection configured. Any CA can issue certificates and no brand logo verification in place.

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

Mail Transport Security Beta Is mail transport encrypted and verified? Not Enforced

Port 25 not reachable from this host

MX Host STARTTLS TLS Version Cipher Certificate
_dc-mx.c7ca266953f1.mobilecommercepress.com N/A N/A N/A
SMTP port 25 may be blocked by hosting provider — this is common for cloud platforms
Summary: 0/1 reachable, 0 STARTTLS, 0 valid certs
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

ASNNameCountry
AS13335 US
IPv4 Mappings:
172.67.200.8 → AS13335 (172.67.192.0/20)
104.21.36.226 → AS13335 (104.21.32.0/19)
IPv6 Mappings:
2606:4700:3034::6815:24e2 → AS13335 (2606:4700:3034::/48)
2606:4700:3037::ac43:c808 → AS13335 (2606:4700:3037::/48)

Edge / CDN Success Cloudflare

Domain is behind Cloudflare edge network

Behind CDN Origin Hidden
ASN 13335 belongs to Cloudflare

SaaS TXT Footprint Success 1 service

1 SaaS service(s) detected via TXT record verification

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

ServiceVerification Record
Google Workspace google-site-verification=RVnDiA0a4kQFvJBtV90DUNt72XK2W_VgDkMMHgg0coc
Domain Security Methodology Can DNS responses be tampered with in transit?

DNSSEC RFC 4033 §2 Verified Unsigned

DNSSEC not configured - DNS responses are unsigned

Domain does not use DNSSEC. Enable in your registrar's DNS settings (look for "DNSSEC" or "DS records" section).

NS Delegation Verified

2 nameserver(s) configured

Nameservers: robert.ns.cloudflare.com vida.ns.cloudflare.com
Multi-Resolver Verification Recon: Consensus reached - 4 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records

HTTPS / SVCB Records RFC 9460 Success HTTPS HTTP/3 ECH

HTTPS records found, HTTP/3 supported, ECH (Encrypted Client Hello) enabled

PriorityTargetALPNECHRaw
1 . h3, h2 Yes mobilecommercepress.com. 300 IN HTTPS 1 . alpn="h3,h2" ipv4hint="104.21.36.226,172.67.200.8" ech="AEX+DQBB4QAgACBYex2QJRlLuMeMf+LTXzJmMC/bQOBAmMKa45E5dv0wLgAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA=" ipv6hint="2606:4700:3034::6815:24e2,2606:4700:3037::ac43:c808"
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

172.67.200.8
104.21.36.226
Where the domain points for web traffic

AAAAIPv6 Address

2606:4700:3034::6815:24e2
2606:4700:3037::ac43:c808
IPv6 ready

MXMail Servers

0 _dc-mx.c7ca266953f1.mobilecommercepress.com.
Priority + mail server for email delivery

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (2 IPv4, 2 IPv6) Mail: 1 server Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 9 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).
Re-Analyze to Retry CT Lookup
276 certificates analyzed current expired Source: Certificate Transparency Logs
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
CT Log Expired — 20 — —
CT Log Expired — 8 — —
CT Log Expired — 8 — —
CT Log Expired — 20 — —
CT Log Expired — 21 — —
CT Log Expired — 20 — —
CT Log Expired — 20 — —
CT Log Expired — 20 — —
CT Log Expired — 21 — —
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 2 / 2 records
172.67.200.8
172.67.200.8
104.21.36.226
104.21.36.226
AAAA Synchronized 2 / 2 records
2606:4700:3034::6815:24e2
2606:4700:3037::ac43:c808
2606:4700:3037::ac43:c808
2606:4700:3034::6815:24e2
CAA RFC 8659 §4 0 / 0 records
No records
No records
MX RFC 5321 Synchronized 1 / 1 records
0 _dc-mx.c7ca266953f1.mobilecommercepress.com.
0 _dc-mx.c7ca266953f1.mobilecommercepress.com.
NS RFC 1035 Synchronized 2 / 2 records
robert.ns.cloudflare.com.
robert.ns.cloudflare.com.
vida.ns.cloudflare.com.
vida.ns.cloudflare.com.
SOA RFC 1035 Synchronized 1 / 1 records
robert.ns.cloudflare.com. dns.cloudflare.com. 2393331679 10000 2400 604800 1800
robert.ns.cloudflare.com. dns.cloudflare.com. 2393331679 10000 2400 604800 1800
TXT RFC 7208 §4 Synchronized 2 / 2 records
google-site-verification=RVnDiA0a4kQFvJBtV90DUNt72XK2W_VgDkMMHgg0coc
google-site-verification=RVnDiA0a4kQFvJBtV90DUNt72XK2W_VgDkMMHgg0coc
v=spf1 ip4:72.52.246.3 +a +mx +ip4:129.121.178.52 +include:relay.mailchannels.net +include:relay.mailchannels.net +include:bluehost.com ~all
v=spf1 ip4:72.52.246.3 +a +mx +ip4:129.121.178.52 +include:relay.mailchannels.net +include:relay.mailchannels.net +include:bluehost.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), SecurityTrails (DNS history), 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.

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

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 172.67.200.8 (Team Cymru) 
dig +short 8.200.67.172.origin.asn.cymru.com TXT
ASN lookup for 104.21.36.226 (Team Cymru) 
dig +short 226.36.21.104.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 4874 runs
DKIM
Verified 4692 runs
DMARC
Verified 4857 runs
DANE/TLSA
Verified 4676 runs
DNSSEC
Verified 4855 runs
BIMI
Verified 4691 runs
MTA-STS
Verified 4694 runs
TLS-RPT
Verified 4696 runs
CAA
Verified 4688 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 mobilecommercepress.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer mobilecommercepress.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer mobilecommercepress.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer mobilecommercepress.com NS
Query TXT records (RFC 1035) 
dig +noall +answer mobilecommercepress.com TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 172.67.200.8 (Team Cymru) 
dig +short 8.200.67.172.origin.asn.cymru.com TXT
ASN lookup for 104.21.36.226 (Team Cymru) 
dig +short 226.36.21.104.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

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