Skip to content
https://mysanantonio.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
1
REVIEW
6
PASS
2
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
2 PASS 6 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 1273 ms total
REVIEW
1 redirect(s), 1273 ms total
Info::
Single redirect
Got: https://mysanantonio.com → https://www.mysanantonio.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1273 ms total
Got: 1273 ms

https://mysanantonio.com

909 ms · HTTP/1.1

301

https://www.mysanantonio.com/

364 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mysanantonio.com301909 msHTTP/1.1Apache/2.4.58
2https://www.mysanantonio.com/200364 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 957 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 957 B Sitemaps referenced 2 User-agents ai2bot-dolma, bytespider, claude-user, duckassistbot, friendlycrawler, youbot, kangaroo-bot, *, claude-web, cohere-ai, diffbot, omgilibot, anthropic-ai, perplexity-user, perplexitybot, scrapy, timpibot, applebot-extended, ccbot, claudebot, omgili, webzio-extended, AmazonAdBot Blocking No — crawling allowed
Sitemap: https://www.mysanantonio.com/sitemap.xml
Sitemap: https://www.mysanantonio.com/sitemap_news.xml

User-agent: ai2bot-dolma
User-agent: anthropic-ai
User-agent: applebot-extended
User-agent: bytespider
User-agent: ccbot
User-agent: claude-user
User-agent: claude-web
User-agent: claudebot
User-agent: cohere-ai
User-agent: diffbot
User-agent: duckassistbot
User-agent: friendlycrawler
User-agent: omgili
User-agent: omgilibot
User-agent: perplexity-user
User-agent: perplexitybot
User-agent: scrapy
User-agent: timpibot
User-agent: youbot
User-agent: webzio-extended
User-agent: kangaroo-bot
Disallow: /

User-agent: AmazonAdBot
Allow: /

User-agent: *
Disallow: /business/press-releases/
Disallow: /style/beauty/hearstmagazines/
Disallow: /style/fashion/hearstmagazines/
Disallow: /living/relationships/hearstmagazines/
Disallow: /homeandgarden/home/hearstmagazines/
Disallow: /living/wellness/hearstmagazines/
Disallow: /search
Disallow: /413gkwMT/
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.mysanantonio.com/
200https://mysanantonio.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Connection waterfall

DNS Lookup 393 ms TCP Connect 250 ms TLS Handshake 251 ms Server Processing 249 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
79 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
A
DNS Records
4 A records, 1311 ms lookup
PASS
4 A records, 1311 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 34.235.224.231, 34.197.233.251, 34.198.86.45, 34.204.119.243
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns5.hearstnp.com, ns2.hearstnp.com, ns1.hearstnp.com, ns3.hearstnp.com, ns4.hearstnp.com, ns6.hearstnp.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (1311 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1311 ms
A34.235.224.231, 34.197.233.251, 34.198.86.45, 34.204.119.243
AAAA—
CNAME—
NSns5.hearstnp.com, ns2.hearstnp.com, ns1.hearstnp.com, ns3.hearstnp.com, ns4.hearstnp.com, ns6.hearstnp.com
MX
10 mysanantonio-com.mail.protection.outlook.com
TXT
tollbit-domain-verification=f0781c542a8230ad8cfbcff7f5ca0771d74789baf2db91ec3ba5...
google-site-verification=H4A12fETgPrYAnTnGjQUu7g2G0SdfllUwsnR3RhNodQ
google-site-verification=XU7DrLFw3RrBsJr_8S25Ut_v9dvCxJfSgdXzinSJees
facebook-domain-verification=cqvjqqfgfqut6ltmlxraww2e5z3zqr
f90dae01b1b44f1e985cdcf38f5f8ed6
google-site-verification=kSWPe4ui2mM3gAWoscQQBIX7shXJCnZQuvzrSgJyMx8
EIN/7z6bR+Ywp2g42nVEkhxkGVU5pVXHD9Z6TPdAGUKsQglLNrjVbAAzeEGfSXgqe9g8dUk17mmYSeUv...
q13422uho7as37br5kt61spk7b
MS=ms18543610
SPF v=spf1 ip4:74.203.49.125 include:spf.protection.outlook.com ip4:205.220.176.159 ...
_globalsign-domain-verification=Iiihy-iv_vLdlIMtHvh-aCdqO2T53oCoknhW44njXn
facebook-domain-verification=62k60f8ca64igbuy9y3mvox77cx98s
google-site-verification=CfckSdHvUUc5hI52k0cK3YFWfZq-5RXhFTB2dLRHm8Q
cdac6uin8qhdq94ednb175dptn
BSI103498586397
google-site-verification=a3Q4bR618Y_TdKd9w5vTct0etJVT0tDqGsq0ISiU9yo
google-site-verification=hn3psYpK-rLL1cgHcPdAqdp5iqenJsWqBKJtz2kgqak
CAALookup not available with standard resolver
Resolved in 1311 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Domain Intelligence
mysanantonio.com — via CSC Corporate Domains, Inc., 27 years, 6 months old, hosted on AWS
PASS
mysanantonio.com — via CSC Corporate Domains, Inc., 27 years, 6 months old, hosted on AWS
Info::
Domain registered until Feb 22, 2027 (10 months 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: CSC Corporate Domains, 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: AWS
Got: AS14618
Domain expiry

222 days

February 22, 2027

SSL certificate

79 days

Issued by Let's Encrypt

Domain age

27 years, 6 months

Registered February 22, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

34.198.86.45

Registrar

CSC Corporate Domains, 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 CSC Corporate Domains, Inc.
Created February 22, 1999 (27 years, 6 months ago)
Expires February 22, 2027 (10 months)
Last Updated February 18, 2026
Name Servers ns1.hearstnp.com, ns2.hearstnp.com, ns3.hearstnp.com, ns4.hearstnp.com, ns5.hearstnp.com, ns6.hearstnp.com
DNSSEC Not enabled
Hosting
IP Address 34.198.86.45
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.9s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback