Skip to content
https://villadentaltexas.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
11
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
6 PASS 11 REVIEW
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 192.185.35.207 does not match any cert SAN: 192-185-35-207.unifiedlayer.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.
B
Multi-Resolver DNS Speed
Mean 107ms across 3 resolvers (spread 158ms)
REVIEW
Mean 107ms across 3 resolvers (spread 158ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Quad9: 125ms
Got: 125ms via 9.9.9.9:53
Info::
Cloudflare: 178ms
Got: 178ms via 1.1.1.1:53
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

200http://villadentaltexas.com/

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
58 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

58
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
C
CDN & Delivery
Action
Assets on Cloudflare (host cdnjs.cloudflare.com, 8 assets); document served directly from origin (Oracle Cloud)
REVIEW
Assets on Cloudflare (host cdnjs.cloudflare.com, 8 assets); document served directly from origin (Oracle Cloud)
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (cdnjs.cloudflare.com, 8 assets), but the HTML document itself comes straight from the origin (Oracle Cloud). Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a5a45eb92f14f533-CDG
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 8), cache HIT
Got: cf-ray: a5a45eb92f14f533-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin Oracle Cloud

Asset hosts on a CDN

  • cdnjs.cloudflare.com — Cloudflare · assets: 8 · Cache Status: HIT

Other asset hosts

  • fonts.googleapis.com — assets: 4 · Google

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 111 ms lookup
PASS
1 A records, 111 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.185.35.207
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns8090.hostgator.com, ns8089.hostgator.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 111 ms
Got: 111 ms
A192.185.35.207
AAAA—
CNAME—
NSns8090.hostgator.com, ns8089.hostgator.com
MX
0 villadentaltexas.com
TXT
SPF v=spf1 a mx include:websitewelcome.com ~all
CAALookup not available with standard resolver
Resolved in 111 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://villadentaltexas.com

https://villadentaltexas.com

298 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://villadentaltexas.com200298 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 177 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
Sitemap index with 5 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 177 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: http://villadentaltexas.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 5 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
villadentaltexas.com — via GoDaddy.com, LLC, 13 years old, hosted on Oracle Cloud
PASS
villadentaltexas.com — via GoDaddy.com, LLC, 13 years old, hosted on Oracle Cloud
Warning::
Domain expires in 53 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jan 6, 2027
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: GoDaddy.com, LLC
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: Oracle Cloud
Got: AS31898
Domain expiry

53 days

January 6, 2027

SSL certificate

58 days

Issued by Let's Encrypt

Domain age

13 years

Registered January 6, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Oracle Cloud

ASN AS31898

192.185.35.207

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created January 6, 2014 (13 years ago)
Expires January 6, 2027 (1 months)
Last Updated January 7, 2026
Name Servers ns8089.hostgator.com, ns8090.hostgator.com
DNSSEC Not enabled
Hosting
IP Address 192.185.35.207
ASN AS31898 (ORACLE-BMC-31898 - Oracle Corporation, US)
Provider Oracle Cloud
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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
HTTP Probe Timing
Total 513 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
112 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
95 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
98 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
418 ms
Total Time Total request time from DNS lookup through full response.
513 ms

Connection waterfall

DNS Lookup 112 ms TCP Connect 95 ms TLS Handshake 98 ms Server Processing 114 ms Content Transfer 95 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback