Skip to content
https://www.vanguardmexico.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 10 REVIEW
B
DNS Records
2 A records, 33 ms lookup
REVIEW
2 A records, 33 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.211.15.132, 23.211.15.157
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.vanguardmexico.com.edgekey.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 33 ms
Got: 33 ms
A23.211.15.132, 23.211.15.157
AAAA—
CNAMEwww.vanguardmexico.com.edgekey.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 33 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 23.211.15.132 does not match any cert SAN: a23-211-15-132.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 23.211.15.157 does not match any cert SAN: a23-211-15-157.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
HTTP Probe Timing
Total 886 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
83 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
110 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
870 ms
Total Time Total request time from DNS lookup through full response.
886 ms

Connection waterfall

DNS Lookup 83 ms TCP Connect 1 ms TLS Handshake 110 ms Server Processing 676 ms Content Transfer 16 ms
B
TLS Certificate Expiry & Recommendations
52 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

52
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Document on Akamai; assets also on AWS CloudFront
REVIEW
Document on Akamai; assets also on AWS CloudFront
Info::
Document is served via Akamai CDN
Got: delegation www.vanguardmexico.com.edgekey.net
Info::
Assets on AWS CloudFront: corp.etm.assets.vgdynamic.info (assets: 4), cache RefreshHit from cloudfront
Got: x-amz-cf-id: dKreZwMnd_56Phz2Kbha5gMAxVUO9zJuwW1isUHAtfPc3ESXK7kIDg==
Document served via CDN: Akamai
Provider Akamai Evidence delegation www.vanguardmexico.com.edgekey.net

Asset hosts on a CDN

  • corp.etm.assets.vgdynamic.info — AWS CloudFront · assets: 4 · Cache Status: RefreshHit from cloudfront

Other asset hosts

  • mdl-medallia-digital.vanguard.com — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 45ms across 3 resolvers (spread 42ms)
PASS
Mean 45ms across 3 resolvers (spread 42ms)
Info::
Quad9: 24ms
Got: 24ms via 9.9.9.9:53
Info::
Google: 47ms
Got: 47ms via 8.8.8.8:53
Info::
Cloudflare: 66ms
Got: 66ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 489 ms total
PASS
1 redirect(s), 489 ms total
Info::
Single redirect
Got: https://www.vanguardmexico.com → https://www.vanguardmexico.com/es/inicio (301)

https://www.vanguardmexico.com

191 ms · HTTP/1.1

301

https://www.vanguardmexico.com/es/inicio

298 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.vanguardmexico.com301191 msHTTP/1.1
2https://www.vanguardmexico.com/es/inicio200298 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 305 URLs
PASS
robots.txt present, sitemap with 305 URLs
Info::
robots.txt is present
Got: 719 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 305 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 719 B Sitemaps referenced 2 User-agents *, Claude-SearchBot, bingbot, ChatGPT-User, Google-Extended, OAI-SearchBot, PerplexityBot, GPTBot, ClaudeBot Blocking No — crawling allowed
# Default crawl policy — allow all crawlers
User-agent: *
Disallow:

# --- AI search & citation crawlers: explicitly allowed ---
# These bots surface site content in AI-generated answers and citations.
User-agent: OAI-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: bingbot
Allow: /

# --- AI model-training crawlers: blocked ---
# Prevent site content from being used to train large language models.
User-agent: GPTBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Google-Extended
Disallow: /

Sitemap: https://www.vanguardmexico.com/en/sitemap.xml
Sitemap: https://www.vanguardmexico.com/es/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 305 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.vanguardmexico.com/
301https://vanguardmexico.com/

Preferred variant: www

HTTP → HTTPS

301http://www.vanguardmexico.com/ → https://www.vanguardmexico.com/

Consistent

A+
Domain Intelligence
vanguardmexico.com — via MarkMonitor Inc., 18 years, 2 months old, hosted on Akamai
PASS
vanguardmexico.com — via MarkMonitor Inc., 18 years, 2 months old, hosted on Akamai
Info::
Domain registered until Nov 10, 2028 (2 years remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: Akamai
Got: AS20940
Domain expiry

733 days

November 10, 2028

SSL certificate

52 days

Issued by Let's Encrypt

Domain age

18 years, 2 months

Registered November 10, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS20940

23.211.15.132

Registrar

MarkMonitor Inc.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created November 10, 2008 (18 years, 2 months ago)
Expires November 10, 2028 (2 years)
Last Updated October 9, 2026
Name Servers a1-96.akam.net, a12-65.akam.net, a16-67.akam.net, a4-65.akam.net, a7-66.akam.net, a9-67.akam.net
DNSSEC Not enabled
Hosting
IP Address 23.211.15.132
ASN AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL)
Provider Akamai
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
Health Check Endpoint
Health endpoint at https://www.vanguardmexico.com/health (HTTP 200)
PASS
Health endpoint at https://www.vanguardmexico.com/health (HTTP 200)
Info::
Public health endpoint at https://www.vanguardmexico.com/health
Got: https://www.vanguardmexico.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback