Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 17 Feb 2026, 14:21 UTC
Duration 2.7s
Version v26.19.21
Integrity 43d68322dcac1fb40a395e121b5b4addd264f507144d5e7bcb304aab989445a5f4a6486b8a405133e8ee45daa2fab5b6fa8af2f98a78ed58968b2214bf18728d
Subject Domain
mercadopago.com

Engineer's DNS Intelligence Report

mercadopago.com
17 Feb 2026, 14:21 UTC · 2.7s ·v26.19.21 · SHA-3-512: 43d6✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint Amazon Route 53 Google Workspace 6 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
5 protocols configured, 3 not configured, 1 unavailable on provider Why we go beyond letter grades
Suggested Scanner Configuration High Confidence
Based on 11 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 33.0s, 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
Protected
Brand Impersonation
Protected
DNS Tampering
Enterprise
Certificate Control
Configured
Configured
SPF, DMARC (reject), DKIM, BIMI, CAA
Not Configured
MTA-STS, TLS-RPT, DNSSEC
Unavailable on Provider
DANE
Priority Actions Achievable posture: Secure
Medium Enable DNSSEC

DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.

RFC 4035
Low Add TLS-RPT Reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.

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

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

MTA-STS tells sending servers to require TLS when delivering mail to your domain.
TypeTXT
Host_mta-sts.mercadopago.com (MTA-STS policy record)
Valuev=STSv1; id=mercadopago.com
RFC 8461
Registrar (RDAP) OBSERVED LIVE
MarkMonitor Inc.
Registrar for mercadopago.com
Email Service Provider
Google Workspace
Strongly Protected
Web Hosting
AWS CloudFront
Where website is hosted
DNS Hosting
Amazon Route 53 Enterprise
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:spfa.mercadopago.com ip4:172.217.0.0/19 ip4:172.217.128.0/19 ip4:172.217.160.0/20 ip4:172.217.192.0/19 ip4:172.217.32.0/20 ip4:172.253.112.0/20 ip4:172.253.56.0/21 ip4:18.211.176.124 ip4:18.211.61.67 ip4:18.213.72.148 ip4:184.73.44.157 ~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; rua=mailto:dmarcrua@mercadolibre.com, mailto:mercadolibre@rua.netcraft.com, mailto:dmarc_agg@vali.email; ruf=mailto:dmarcruf@mercadolibre.com,mailto:mercadolibre@ruf.netcraft.com; adkim=s; aspf=r; rf=afrf; pct=100;
Alignment: SPF relaxed DKIM strict
No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing
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

Found DKIM records for 4 selector(s)

google._domainkey Google Workspace
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCCO2Z3F/WstmJVCJVsFKxj+Z75FSGC+pf1+EYYppDMRtBk4833wBdyHOiJqfSO/3aeMY+c9gxUlky35a4JI6/DvA11qhkdkuEiF+0kNY5RjhEsDF2+feXSqJ9arDrRH9GSqDE5wo4dxzBSb0FHdEpc9Ls1Q4nImJP6HbaIMYxSGQIDAQAB
mx._domainkey
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeBvT2WAVCbWqbzeWMZvKy2ino5ilepY4gTaNWirjM1sQYnO4V5qMZs5ZuNUALEjHf9B1zKVsX3NnHQf45emwDLEZBXrzrPQKnguTFWaUvG03dOfnd9Dt+imV6IDTirBbKyYPMOc9os147GlEsBOlNj69+EAJ0roHlDIxGjb+QFwIDAQAB
s1._domainkey SendGrid
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9N9cLWGA0SOTUAUsvGk7GColStKU7Gh1DGOTSlvehMRNFJwcjS+LCyWG3risedZcJ+QI7ZZH5OGP1SlSNFRfPV4JsGUwjD9kTXF2tEq45PcOvn/Pm9P9p6rQbZ3CrhCnvh/l81bpN4AGj9oCsJytiuPDL9ic8Sy/Cio+sf9opQklqp16a3rtZUZjFb3/hWvwhw6+dKjLk2RdFmdtFcXaSvq/mCd93pQGvt/+njPHt5h4rsVTEULGd/h2CpLC9KsCGUkGbYHbAYG0PrxEYtWVlHS4eDXLdtuqJdio/qGO0FAxbu6M+M2hb4rZyCvNKeKFvynP/kDvhLTDkfo7+DoEYQIDAQAB
s2._domainkey SendGrid
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDDhvrOvKPNpw0s8VpsvQ800soxurpjg0SiJY1svD+xOGApMF7eqWXLoVebu4MealmkIXf5XzNbHTMYmDF9HNbYNA6icymhUYJjD72ikYOwo9NDyU8a6j7+3VW8eeOy9rmC8G37pLIgTskmqZNVdmOtabBJp66TfWnuTi8APPdSUQIDAQAB
RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).
Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Verified

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No MTA-STS record found

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

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

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
mercadolibre.com Authorized v=DMARC1
ruf.netcraft.com Authorized v=DMARC1;
DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — 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).

Brand Security Can this brand be convincingly faked? No DMARC reject policy enforced, BIMI brand verification active, and certificate issuance restricted by CAA

BIMI BIMI Spec Verified Success VMC SVG

Is the brand identity verified and displayed in inboxes? Yes

BIMI with VMC certificate (from Verified CA)

VMC certificate accessible (from Verified CA) - logo displays in Gmail, Apple Mail, and all major providers.
v=BIMI1; l=https://vmc.digicert.com/305c1171-ddd8-4209-ae5d-270629f2abb6.svg; a=https://vmc.digicert.com/305c1171-ddd8-4209-ae5d-270629f2abb6.pem
BIMI Logo
Logo validated (SVG) View full logo

CAA RFC 8659 §4 Verified Success IODEF

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only Amazon, DigiCert can issue certificates

Authorized CAs: Amazon DigiCert
0 iodef "mailto:domains@mercadolibre.com"
0 issue "amazon.com"
0 issue "digicert.com"
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.
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

security.txt properly configured

Contact

mailto:bugbounty@mercadolibre.com

Expires

2026-03-01 Valid

Policy

https://hackerone.com/mercadolibre
en,es Canonical URL Acknowledgments
Source: https://mercadopago.com/security.txt
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

No significant AI surface findings

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? No directives
No robots.txt found
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
Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

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

Transport security inferred from 1 signal(s) — no enforcement policy active

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
Skipped — SMTP probe skipped — outbound TCP port 25 is blocked by cloud hosting provider. This is standard for all major cloud platforms (AWS, GCP, Azure, Replit) as an anti-spam measure. Transport security is assessed via DNS policy records above, which is the standards-aligned primary method per NIST SP 800-177 Rev. 1.
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

ASNNameCountry
AS16509 Amazon.com, Inc. US
IPv4 Mappings:
13.226.2.53 → AS16509 (13.226.0.0/21)
13.226.2.29 → AS16509 (13.226.0.0/21)
13.226.2.4 → AS16509 (13.226.0.0/21)
13.226.2.18 → AS16509 (13.226.0.0/21)

Edge / CDN Success Amazon CloudFront

Domain is served through Amazon CloudFront

Behind CDN Origin Visible
ASN 16509 is Amazon CloudFront

SaaS TXT Footprint Success 6 services

Detected 6 SaaS 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
Miro miro-verification=2a505fedfeda2411c7c140f1cba9c895aa186d78
Facebook facebook-domain-verification=ailwwfbe52ps1ilym4kjmhw9aevy8p
Google google-site-verification=8lKKIFEqxnxxPL0STk6Tt220qZHx0RYsG3jEUdQl-eM
Microsoft MS=ms88267512
Statuspage status-page-domain-verification=c10s9rsq9sr9
Postman postman-domain-verification=06fe2e16be334d546de57dd3932ab61ace1e0abd8ad306dcb2d6e51de4371c3a59d8864f00f5c52d4ec6451a5e1a...
Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

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

4 nameserver(s) configured

Nameservers: ns-1084.awsdns-07.org ns-1599.awsdns-07.co.uk ns-283.awsdns-35.com ns-787.awsdns-34.net
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (2 differences found)
Resolver Differences:
TXT: OpenDNS returned different results: [3kj9311cxtpn8p7bfn9lglc6zl6tyjpp 6300afa29a6047edb6551db692a9c9d2 MS=ms88267512 Ms=ms16336698 b4e2f40762484acfbe1ce1124a04d363 dbd0f8a518a54254a4c22edfc70333e5 gj0mlr4n9sdplx0qhvlns0lm5kb8kdy0 lbv43d83q9w0yqdfx5gr4wdzpvznxq2w lsz1wy99y8sr6nms4b0ybz3y238zxfv9 status-page-domain-verification=c10s9rsq9sr9 zy3fvckb58z69j4rqjvczbkt52bcw6bv]
A: Cloudflare returned different results: [3.170.185.107 3.170.185.35 3.170.185.65 3.170.185.96]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

13.226.2.53
13.226.2.29
13.226.2.4
13.226.2.18
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

5 alt2.aspmx.l.google.com.
5 alt1.aspmx.l.google.com.
10 aspmx3.googlemail.com.
10 aspmx2.googlemail.com.
1 aspmx.l.google.com.
Priority + mail server for email delivery
Google Workspace

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (4 IPv4, 0 IPv6) Mail: 5 servers Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 14 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
CT logs unavailable 14 current 0 expired 13 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)
analytics.mercadopago.com DNS Current d1u27hy6qa1s0l.cloudfront.net — — —
api.mercadopago.com DNS Current nginx-router-api-alb-184275745.us-east-1.elb.amazonaws.com — — —
auth.mercadopago.com DNS Current d1u27hy6qa1s0l.cloudfront.net — — —
beta.mercadopago.com DNS Current d1u27hy6qa1s0l.cloudfront.net — — —
blog.mercadopago.com DNS Current du9uwk62a92xq.cloudfront.net — — —
chat.mercadopago.com DNS Current d1u27hy6qa1s0l.cloudfront.net — — —
demo.mercadopago.com DNS Current du9uwk62a92xq.cloudfront.net — — —
mail.mercadopago.com DNS Current e3.emarsys.net — — —
mobile.mercadopago.com DNS Current — — — —
partners.mercadopago.com DNS Current d1u27hy6qa1s0l.cloudfront.net — — —
sandbox.mercadopago.com DNS Current d1u27hy6qa1s0l.cloudfront.net — — —
staging.mercadopago.com DNS Current d1u27hy6qa1s0l.cloudfront.net — — —
status.mercadopago.com DNS Current tlmzz6y186mm.stspg-customer.com — — —
www.mercadopago.com DNS Current du9uwk62a92xq.cloudfront.net — — —
Export Recon (CSV)
Δ Changes Detected: A Resolver ≠ Authoritative (TTL / CDN rotation / recent change)
Risk: Low - typically resolves within TTL
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 Propagating 4 / 4 records
13.226.2.53
99.84.118.128
13.226.2.29
99.84.118.91
13.226.2.4
99.84.118.33
13.226.2.18
99.84.118.76
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 Synchronized 3 / 3 records
0 issue "digicert.com"
0 iodef "mailto:domains@mercadolibre.com"
0 issue "amazon.com"
0 issue "amazon.com"
0 iodef "mailto:domains@mercadolibre.com"
0 issue "digicert.com"
DMARC _dmarc.mercadopago.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; rua=mailto:dmarcrua@mercadolibre.com, mailto:mercadolibre@rua.netcraft.com, mailto:dmarc_agg@vali.email; ruf=mailto:dmarcruf@mercadolibre.com,mailto:mercadolibre@ruf.netcraft.com; adkim=s; aspf=r; rf=afrf; pct=100;
v=DMARC1; p=reject; rua=mailto:dmarcrua@mercadolibre.com, mailto:mercadolibre@rua.netcraft.com, mailto:dmarc_agg@vali.email; ruf=mailto:dmarcruf@mercadolibre.com,mailto:mercadolibre@ruf.netcraft.com; adkim=s; aspf=r; rf=afrf; pct=100;
MX RFC 5321 Synchronized 5 / 5 records
5 alt2.aspmx.l.google.com.
1 aspmx.l.google.com.
5 alt1.aspmx.l.google.com.
10 aspmx2.googlemail.com.
10 aspmx3.googlemail.com.
10 aspmx3.googlemail.com.
10 aspmx2.googlemail.com.
5 alt1.aspmx.l.google.com.
1 aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
NS RFC 1035 Synchronized 4 / 4 records
ns-787.awsdns-34.net.
ns-1084.awsdns-07.org.
ns-1084.awsdns-07.org.
ns-1599.awsdns-07.co.uk.
ns-1599.awsdns-07.co.uk.
ns-283.awsdns-35.com.
ns-283.awsdns-35.com.
ns-787.awsdns-34.net.
SOA RFC 1035 Synchronized 1 / 1 records
ns-1084.awsdns-07.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
ns-1084.awsdns-07.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
TXT RFC 7208 §4 22 / 0 records
Ms=ms16336698
—
zy3fvckb58z69j4rqjvczbkt52bcw6bv
—
3kj9311cxtpn8p7bfn9lglc6zl6tyjpp
—
monday-com-verification=G6gWiJdNb9CBcH8BHiELjqXSmd9b04RarDTXkffu_-k
—
lbv43d83q9w0yqdfx5gr4wdzpvznxq2w
—
miro-verification=2a505fedfeda2411c7c140f1cba9c895aa186d78
—
facebook-domain-verification=ailwwfbe52ps1ilym4kjmhw9aevy8p
—
google-site-verification=8lKKIFEqxnxxPL0STk6Tt220qZHx0RYsG3jEUdQl-eM
—
anthropic-domain-verification-dx91wj=RGAuq1HgKTkCSeVoLx2PNsyHA
—
google-site-verification: ZsJQDbUT0TdjOV7yAEK5nHoczuBWt_ssUu8tky9gfsI
—
b4e2f40762484acfbe1ce1124a04d363
—
v=spf1 include:spfa.mercadopago.com ip4:172.217.0.0/19 ip4:172.217.128.0/19 ip4:172.217.160.0/20 ip4:172.217.192.0/19 ip4:172.217.32.0/20 ip4:172.253.112.0/20 ip4:172.253.56.0/21 ip4:18.211.176.124 ip4:18.211.61.67 ip4:18.213.72.148 ip4:184.73.44.157 ~all
—
google-site-verification=ku3q1eSXNyfwsXOhsi1AcdMPgm18RMzhB-awZQCvjeM
—
gj0mlr4n9sdplx0qhvlns0lm5kb8kdy0
—
google-site-verification=0NofbC90nNRsH8U8VPcR8tlzeyXyrlvN0Lol3zdWFfI
—
MS=ms88267512
—
status-page-domain-verification=c10s9rsq9sr9
—
dbd0f8a518a54254a4c22edfc70333e5
—
lsz1wy99y8sr6nms4b0ybz3y238zxfv9
—
postman-domain-verification=06fe2e16be334d546de57dd3932ab61ace1e0abd8ad306dcb2d6e51de4371c3a59d8864f00f5c52d4ec6451a5e1a7616c820d240faea936d764d32728092a71b
—
pardot977283=ead2f50a7204cf88e26dc4c6817232fb5b70ef06b16e89fc29c74b6824267a4a
—
6300afa29a6047edb6551db692a9c9d2
—
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.

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

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 13.226.2.53 (Team Cymru) 
dig +short 53.2.226.13.origin.asn.cymru.com TXT
ASN lookup for 13.226.2.29 (Team Cymru) 
dig +short 29.2.226.13.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 5037 runs
DKIM
Verified 4856 runs
DMARC
Verified 5021 runs
DANE/TLSA
Verified 4838 runs
DNSSEC
Verified 5019 runs
BIMI
Verified 4852 runs
MTA-STS
Verified 4855 runs
TLS-RPT
Verified 4859 runs
CAA
Verified 4852 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 mercadopago.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer mercadopago.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer mercadopago.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer mercadopago.com NS
Query TXT records (RFC 1035) 
dig +noall +answer mercadopago.com TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 13.226.2.53 (Team Cymru) 
dig +short 53.2.226.13.origin.asn.cymru.com TXT
ASN lookup for 13.226.2.29 (Team Cymru) 
dig +short 29.2.226.13.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

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