Back to results

Digital exposure report

santander.com.mx

High exposure. Significant weaknesses put the brand, customers and email at risk.

Scanned: 2026-11-18 01:55 UTC

Partial coverage: the score is based on 95% of applicable check weight. 1 unverified check(s) are excluded, not counted as failures.

D
62/100

What to do first

  1. 1.

    Send visitors to the secure version of your site

    Visitors who type your address without https may stay on an unprotected connection.

    Who can fix it: Your web host

    How to verify after the fix

    curl -sI http://santander.com.mx/ | grep -iE "^(HTTP|location)"
  2. 2.

    Turn on DNS signing for your domain

    Signing helps resolvers detect forged answers about your domain.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short DS santander.com.mx

A starting point, not a security guarantee.

What this grade means

Tested hostname
santander.com.mx
Website request
GET https://santander.com.mx/
Scan time
2026-11-18 01:55:52 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
  • DKIM — digital signature on email · Not detected (common selectors only)

This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.

Score by category

Email security25/25Spoofing email from this domain is hard.
Encryption & certificate18/25Encryption is in place, but a gap could expose users.
Browser protections13/30Several browser hardening headers are missing, which removes layers of protection against script injection and framing.
DNS infrastructure3/15The domain's infrastructure lacks basic protections.

Fix priorities

  1. 1.HighHTTP → HTTPS redirect · Hardening gap+7
  2. 2.MediumClickjacking protection · Hardening gap+5
  3. 3.MediumDNSSEC — signed DNS records · Hardening gap+7
  4. 4.LowCAA — who may issue certificates · Hardening gap+5
  5. 5.LowX-Content-Type-Options · Hardening gap+4
  6. 6.LowReferrer-Policy · Hardening gap+3
  7. 7.LowPermissions-Policy · Hardening gap+2
  8. 8.LowCSP — protection from script injection · Hardening gap+3

To verify

Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.

  • DKIM — digital signature on email

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 10/10

An authorized sender list is defined and mail from other servers is rejected.

Valid SPF record with -all. 4 of the 10 allowed DNS lookups.

Source data: DNS TXT santander.com.mx
v=spf1 ip4:170.169.137.21 ip4:170.169.137.22 ip4:170.169.130.68 ip4:170.169.130.69 ip4:170.169.130.45 include:protection.outlook.com include:_spf.qualtrics.com exists:%{i}.spf.as.gruposantander.com exists:%{i}.spf.us.gruposantander.com -all
$ dig +short TXT santander.com.mx
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Passed · Severity: OK · 15/15

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

Source data: DNS TXT _dmarc.santander.com.mx
v=DMARC1; p=reject; rua=mailto:santander@rua.dmp.cisco.com,mailto:bitacora_rua@produban.com.mx; ruf=mailto:santander@ruf.dmp.cisco.com,mailto:bitacora_alerts@produban.com.mx; pct=100; fo=1;
$ dig +short TXT _dmarc.santander.com.mx
Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Not detected (common selectors only) · Severity: OK · Not scored

No DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.

A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.

Source data: DNS TXT <selector>._domainkey.santander.com.mx
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found
google._domainkey: nxdomain
selector1._domainkey: nxdomain
selector2._domainkey: nxdomain
default._domainkey: nxdomain
k1._domainkey: nxdomain
s1._domainkey: nxdomain
s2._domainkey: nxdomain
dkim._domainkey: nxdomain
mail._domainkey: nxdomain
smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.santander.com.mx
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail exchangers are published for the domain.

4 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.

Source data: DNS MX santander.com.mx
5 mx1.hc5532-55.iphmx.com
90 mx1.santandergroup.c3s2.iphmx.com
90 mx2.santandergroup.c3s2.iphmx.com
5 mx2.hc5532-55.iphmx.com
$ dig +short MX santander.com.mx
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Passed · Severity: OK · 10/10

The site loads over an encrypted connection.

https://santander.com.mx/ returned HTTP 403 (final URL: https://santander.com.mx/). Client-side certificate validation passed.

Source data: HTTPS GET https://santander.com.mx/
HTTP 403
Final URL: https://santander.com.mx/
$ curl -sIL https://santander.com.mx/
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Failed · Severity: High · Hardening gap · 0/7

The site is also reachable over an unencrypted connection, so data may travel in plain text on public networks.

http://santander.com.mx/ returned HTTP 403 without redirecting to https://.

Source data: HTTP GET http://santander.com.mx/ (redirects not followed)
HTTP 403
Location: (none)
$ curl -sI http://santander.com.mx/ | grep -iE "^(HTTP|location)"
Fix recommendation (effort: Easy)
  1. Set up a permanent (301) redirect from every HTTP request to HTTPS on the server or CDN.
  2. Then add an HSTS header.
server {
  listen 80;
  server_name santander.com.mx www.santander.com.mx;
  return 301 https://$host$request_uri;
}

Safety: This change is made on your server. Make sure HTTPS works first, otherwise the site won't load.

Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Passed · Severity: OK · 8/8

The certificate was accepted by a validating TLS client at scan time.

Live TLS handshake succeeded. Latest issuance in CT logs: DigiCert, expiring 2027-05-08 (171 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.

Source data: Certificate Transparency logs (certspotter) for santander.com.mx
Live TLS handshake: certificate accepted
CT logs (context only, not scored):
Issuer: DigiCert
Valid from: 2026-10-22
Valid until: 2027-05-08
Names: api.santander.com.mx, m.santander.com.mx, santander.com.mx, www.santander.com.mx
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect santander.com.mx:443 -servername santander.com.mx 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Passed · Severity: OK · 8/8

Browsers are told to always use an encrypted connection to the site.

max-age=31536000 (365 days), includeSubDomains, preload. ≥ 180 days recommended.

Source data: Response headers from https://santander.com.mx/
Strict-Transport-Security: max-age=31536000 ; includeSubDomains ; preload
$ curl -sIL https://santander.com.mx/ | grep -i "Strict-Transport-Security"
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Needs attention · Severity: Low · Hardening gap · 5/8

A script policy exists, but it's permissive and offers only partial protection.

script-src includes: 'unsafe-eval' — weakens XSS protection.

Source data: Response headers from https://santander.com.mx/
Content-Security-Policy: default-src 'self' *.doubleclick.net bat.bing.com connect.facebook.net stats.g.doubleclick.net www.google-analytics.com www.google.com www.googleanalytics.com www.googletagmanager.com www.gstatic.com *.santander.com.mx; script-src 'self' 'unsafe-eval' 'wasm-unsafe-eval' blob: *.facebook.com *.g.doubleclick.net *.googleads.g.doubleclick.net *.googletagmanager.com *.gstatic.com *.ojo7.com *.ojo7.ltroute.com ajax.googleapis.com https://analytics.tiktok.com bat.bing.com https://business.tiktok.com https://c.amazon-adsystem.com connect.facebook.net csi.gstatic.com g.microsoft.com maps.google.com ojo7.com ojo7.ltroute.com optimize.google.com https://ssl.google-analytics.com storage.googleapis.com https://*.tt.omtrdc.net https://*.demdex.net https://*.adobe.com tagmanager.google.com tpc.googlesyndication.com https://websdk.appsflyer.com www.google-analytics.com www.google.com www.google.com.mx www.googleadservices.com www.googleanalytics.com https://impressions.onelink.me https://www.googletagmanager.com https://mysantander.onelink.me cpa.leadgid.com *.crazyegg.com *.santander.com.mx *.akstat.io *.go-mpulse.net universal-editor-service.experiencecloud.live universal-editor-service.adobe.io; script-src-elem 'self' 'nonce-base' 'nonce-gtm' blob: *.facebook.com *.g.doubleclick.net *.googleads.g.doubleclick.net *.googletagmanager.com *.gstatic.com *.ojo7.com *.ojo7.ltroute.com ajax.googleapis.com https://maps.googleapis.com https://analytics.tiktok.com bat.bing.com https://business.tiktok.com https://c.amazon-adsystem.com connect.facebook.net csi.gstatic.com g.microsoft.com maps.google.com ojo7.com ojo7.ltroute.com optimize.google.com https://ssl.google-analytics.com storage.googleapis.com https://*.tt.omtrdc.net https://*.demdex.net https://*.adobe.com tagmanager.google.com tpc.googlesyndication.com https://websdk.appsflyer.com www.google-analytics.com www.google.com www.google.com.mx www.googleadservices.com www.googleanalytics.com https://impressions.onelink.me https://mysantander.onelink.me https://tags.tiqcdn.com cpa.leadgid.com *.crazyegg.com *.santander.com.mx *.akstat.io *.go-mpulse.net *.qualtrics.com 'nonce-next-script' 'nonce-plugin-tealium-utag' 'nonce-h-plugin-tealium-utag' 'nonce-event-tracking-csn' 'nonce-calculations-csn' universal-editor-service.experiencecloud.live universal-editor-service.adobe.io https://cdn.experience.adobe.net https://cdn.tinymce.com cdn1.adoberesources.net https://cdnjs.cloudflare.com; connect-src 'self' *.santandermedia.com *.ok-cloud.net *.doubleclick.net wss://*.facebook.com *.facebook.net wss://*.facebook.net https://*.g.doubleclick.net *.google.com *.googleapis.com https://*.googletagmanager.com *.gstatic.com *.makingscience.com *.ojo7.com *.yimg.com https://www.monitoreomedios.mx https://ad.admitad.com https://ad.doubleclick.net https://analytics.google.com https://analytics.tiktok.com https://app.appsflyer.com bat.bing.com https://c.amazon-adsystem.com wss://connect.facebook.net https://delta.rocket.la https://engagements.appsflyer.com https://googleads.g.doubleclick.net https://leadgenios.net ojo7.com ojo7.ltroute.com https://pagead2.googlesyndication.com https://region1.analytics.google.com https://region1.google-analytics.com https://s.amazon-adsystem.com secure.adnxs.com https://stats.g.doubleclick.net https://storage.googleapis.com https://websdk.appsflyer.com https://impressions.onelink.me www.facebook.com www.google-analytics.com https://www.google.com www.googleadservices.com www.googletagmanager.com https://*.demdex.net https://*.adobe.com https://mysantander.onelink.me cpa.leadgid.com *.crazyegg.com ara.paa-reporting-advertising.amazon *.santander.com.mx www.google.com.mx *.tt.omtrdc.net *.akstat.io *.go-mpulse.net *.qualtrics.com https://cdn.experience.adobe.net; style-src 'self' 'unsafe-inline' *.g.doubleclick.net *.googleapis.com tagmanager.google.com www.google-analytics.com www.google.com *.santander.com.mx https://script.crazyegg.com https://impressions.onelink.me https://*.tt.omtrdc.net https://*.demdex.net https://*.adobe.com crazyegg.com https://mysantander.onelink.me https://cdn.experience.adobe.net https://universal-editor-service.adobe.io; img-src 'self' data: *.mathtag.com *.santandermedia.com i.ytimg.com *.adnxs.com https://*.analytics.google.com *.bat.bing.com *.bing.com *.doubleclick.net *.facebook.com *.google.com *.googleapis.com *.googletagmanager.com *.gstatic.com *.ojo7.com *.ojo7.ltroute.com https://ad.doubleclick.net https://ade.googlesyndication.com https://analytics.tiktok.com https://api.coru.com https://api.mx.alprestamo.io https://assets.santandermedia.com https://bat.bing.com connect.facebook.net https://delta.rocket.la https://googleads.g.doubleclick.net https://leadgenios.net https://multigenios.eo.page https://s.amazon-adsystem.com https://ssl.gstatic.com https://*.tt.omtrdc.net https://*.demdex.net https://*.adobe.com *.crazyegg.com stats.g.doubleclick.net https://www.facebook.com www.google-analytics.com www.google.com www.google.com.mx https://impressions.onelink.me https://mysantander.onelink.me cpa.leadgid.com https://cdn.optinmonster.com *.santander.com.mx assets.santander.com.mx https://www.googleadservices.com; font-src 'self' data: fonts.gstatic.com https://mysantander.onelink.me *.santander.com.mx https://cdn.experience.adobe.net; media-src 'self' *.santandermedia.com *.youtube.com stats.g.doubleclick.net www.google-analytics.com www.google.com https://script.crazyegg.com https://impressions.onelink.me https://mysantander.onelink.me *.santander.com.mx; frame-src 'self' *.youtube.com *.doubleclick.net *.facebook.com https://www.google.com.mx https://googletagmanager.com https://tagmanager.google.com https://td.doubleclick.net https://www.facebook.com www.google.com https://*.tt.omtrdc.net https://*.demdex.net https://*.adobe.com https://script.crazyegg.com https://impressions.onelink.me https://www.googletagmanager.com *.santander.com.mx *.crazyegg.com https://hipotecasantander.com.mx https://www.autocompara.com; object-src 'self' *.santander.com.mx www.youtube.com;
$ curl -sIL https://santander.com.mx/ | grep -i "Content-Security-Policy"
Fix recommendation (effort: Complex)
  1. First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
  2. Collect violations for a week or two and tune the policy to your legitimate sources.
  3. Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/*
  Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'

Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.

Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Failed · Severity: Medium · Hardening gap · 0/5

Missing X-Frame-Options / frame-ancestors: this removes one layer of protection against clickjacking.

No valid X-Frame-Options and no frame-ancestors in the CSP.

Source data: Response headers from https://santander.com.mx/
X-Frame-Options: (missing)
$ curl -sIL https://santander.com.mx/ | grep -i "X-Frame-Options"
Fix recommendation (effort: Easy)
  1. Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
  2. Also set frame-ancestors in the CSP — the modern alternative.
/*
  X-Frame-Options: SAMEORIGIN

Safety: This change is made in your server/CDN settings. Test on staging before production. If partners embed the site in an iframe, add them to frame-ancestors instead of using DENY.

Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Failed · Severity: Low · Hardening gap · 0/4

The browser may interpret files as code unintentionally.

Missing X-Content-Type-Options: nosniff header (MIME sniffing).

Source data: Response headers from https://santander.com.mx/
X-Content-Type-Options: (missing)
$ curl -sIL https://santander.com.mx/ | grep -i "X-Content-Type-Options"
Fix recommendation (effort: Easy)
  1. Add X-Content-Type-Options: nosniff to every response.
/*
  X-Content-Type-Options: nosniff

Safety: This change is made in your server/CDN settings. Test on staging before production.

Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Failed · Severity: Low · Hardening gap · 0/3

Internal URLs (including parameters) may leak to external sites.

Referrer-Policy is missing; the browser will use its default.

Source data: Response headers from https://santander.com.mx/
Referrer-Policy: (missing)
$ curl -sIL https://santander.com.mx/ | grep -i "Referrer-Policy"
Fix recommendation (effort: Easy)
  1. Set Referrer-Policy: strict-origin-when-cross-origin.
/*
  Referrer-Policy: strict-origin-when-cross-origin

Safety: This change is made in your server/CDN settings. Test on staging before production.

Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Needs attention · Severity: Low · Hardening gap · 0/2

Access to sensitive features like the camera and location isn't restricted.

Missing Permissions-Policy header.

Source data: Response headers from https://santander.com.mx/
Permissions-Policy: (missing)
$ curl -sIL https://santander.com.mx/ | grep -i "Permissions-Policy"
Fix recommendation (effort: Easy)
  1. Disable browser features the site doesn't need (camera, microphone, geolocation).
/*
  Permissions-Policy: camera=(), microphone=(), geolocation=()

Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.

Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Software version disclosure

Passed · Severity: OK · unscored

The server doesn't disclose software versions.

No version numbers found in the Server / X-Powered-By headers.

Source data: Response headers from https://santander.com.mx/
server: cloudflare
x-powered-by: (missing)
$ curl -sIL https://santander.com.mx/ | grep -iE "^(server|x-powered-by)"
Documentation: OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Needs attention · Severity: Medium · Hardening gap · 0/7

The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.

No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = false
DS santander.com.mx: NODATA
$ dig +short DS santander.com.mx
Fix recommendation (effort: Medium)
  1. Enable DNSSEC at your DNS provider (one click at most providers).
  2. Copy the DS record your provider generates to your domain registrar.
  3. Wait for propagation and verify with DNSViz.
dig +dnssec santander.com.mx SOA
delv santander.com.mx

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.

Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Needs attention · Severity: Low · Hardening gap · 0/5

Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.

No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.

Source data: DNS CAA santander.com.mx
(no CAA records found)
$ dig +short CAA santander.com.mx
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
santander.com.mx.  CAA  0 issue "letsencrypt.org"
santander.com.mx.  CAA  0 iodef "mailto:security@santander.com.mx"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.

Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

6 NS servers.

Source data: DNS NS santander.com.mx
a1-203.akam.net
a10-67.akam.net
a20-64.akam.net
a28-67.akam.net
a11-64.akam.net
a5-64.akam.net
$ dig +short NS santander.com.mx
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

  • Google & Yahoo sender rules1 unverified
  • PCI DSS v4.03 observed gaps
  • NIS2 / vendor due diligence2 observed gaps
  • SOC 2 / ISO 27001 baseline3 observed gaps

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

Public DNS records

Asantander.com.mx184.30.42.195 | 184.30.42.160
AAAAsantander.com.mx—
MXsantander.com.mx5 mx1.hc5532-55.iphmx.com | 90 mx1.santandergroup.c3s2.iphmx.com | 90 mx2.santandergroup.c3s2.iphmx.com | 5 mx2.hc5532-55.iphmx.com
NSsantander.com.mxa1-203.akam.net | a10-67.akam.net | a20-64.akam.net | a28-67.akam.net | a11-64.akam.net | a5-64.akam.net
TXTsantander.com.mxn4nyny12b95vxf5ggtzkxfxl32dsgnm3 | docusign=37959eee-518a-43aa-b14c-799f0ba9c805 | 9p50qw3gfk78pqdxr5vh61rqm0qjv1v3 | MS=ms65905591 | adobe-idp-site-verification=50935fffec5a7d86b33deb30987909479eb504502ef8be93f8ac75743b3e1f17 | globalsign-domain-verification=86DFDE620BE32D883E16BB90BDC1AF0B | __iic3844zgsssfck1vplc052j3d115ag | atlassian-domain-verification=TFnmCsLwUj4y/ta3Let8OTUy/LAA0o444LEq1oIvcfzM1/BSJ5jdeeKEkTIkTy/x | Dynatrace-site-verification=d0b2c26b-715d-4767-9fc7-d73b290b0dbd__c2411197uelqe0ii2ha6rpimte | 1734589b-a2d4-4c19-8016-9164d8897570 | docusign=50bcf4d0-a098-43d8-8faa-7da22a00edbc | v=spf1 ip4:170.169.137.21 ip4:170.169.137.22 ip4:170.169.130.68 ip4:170.169.130.69 ip4:170.169.130.45 include:protection.outlook.com include:_spf.qualtrics.com exists:%{i}.spf.as.gruposantander.com exists:%{i}.spf.us.gruposantander.com -all | _zm9jas9c0a2148rgotphftmuoqjd08e | globalsign-domain-verification=2B3FDF35AF67C9A9EE1BCAD3559E49F4 | google-site-verification=mVTZ30sb9ol6M-cPtRTsfJmJoGGGoHeV5d-w_JvZYSc | ibmid=3c1d233d-ec45-41df-9aed-e2c457fbfcf3 | Dynatrace-site-verification=8e3733b6-b59c-421f-8b3d-d917200cf7d7__tam9078d2i1cmka36qod053a30 | ae4e16b6a3214667972e38d7113a3c25 | figma-domain-verification=7edc3ebe6cf8433261316f4e9230d9af81459f19b7f5deeec44edc5d1cbe4a9f-1774952452 | yahoo-verification-key=2nUDwpfHQhXhPmayo/N8RUrVrdlIG8eXyYs+gorLpZQ= | _fgysqew1oa7v9uj45vzyzcn240uurwa | Dynatrace-site-verification=d60d17b3-e6a8-496e-bd81-8a8179f81cf2__cm6q9f6amqr42rti4a3qg1pkao | Dynatrace-site-verification=ae885c12-c340-4ae3-be55-dc981c4c4e87__ml831h21olvpu8tdm33v4a1tp7 | Dynatrace-site-verification=d150c9dc-b6b1-458a-98af-73ecce9a03dd__o5n6irdt7i5ui2tdhf85srbr2f | _acme-challenge.segurosapp.t.santander.com.mx. 60 TXT QP_5N3w8iwWUh53H6hunpLy_TfUxHxe9g_ia6qhJHEg | Cyq17IZvuio5u2EiHsXtY0/rp5VhYXc2DspG0nn9EmDBQtWo1GhcRUkpxPP7qECrZ9dDwQZuP7yKcRi5V0uriQ== | google-site-verification=p4wCIQEkFOc7CN7xJc5AZpECoE8xYqPeSrffucACI3Y | Dynatrace-site-verification=ed947660-bda3-492d-abd1-4adef3771938__mhugf75slsedodeqlbbhcissa8 | wxbc5vz8fpz8gd2xmb2616s570rwtjv0 | Dynatrace-site-verification=9a6371d8-6c82-403a-ab96-808f8f6d3f73__21ru2of5o13c95dfpsavpn84oa | 49mp9vqr2bm1q5bv3312t7yz9b265h0g | Dynatrace-site-verification=8831c237-cb92-43f3-b4f6-4f94c2dcc2d3__76u49phhinajj3v8pt2i339k1o | ibmid=e4ae5596-5d61-4c70-bceb-41df13522b4b | Dynatrace-site-verification=3475e819-323b-4c22-9b7f-13608bff6834__t7o4sif8in5tuapk3gikdrp9o9 | atlassian-domain-verification=tsXfopsd9WAe5cfL1rqqdQD/wucWlQvj3974Sm4/FDW6hv5K4l3wICuazbQAkj1a
TXT_dmarc.santander.com.mxv=DMARC1; p=reject; rua=mailto:santander@rua.dmp.cisco.com,mailto:bitacora_rua@produban.com.mx; ruf=mailto:santander@ruf.dmp.cisco.com,mailto:bitacora_alerts@produban.com.mx; pct=100; fo=1;
CAAsantander.com.mx—
DSsantander.com.mx—
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain