Skip to content
https://clinicsofnorthtexas.com/?utm_source=google&utm_medium=organic&utm_campaign=gbp

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 8 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 160.153.0.58 does not match any cert SAN: 58.0.153.160.host.secureserver.net
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
Multi-Resolver DNS Speed
Action
Mean 119ms across 3 resolvers (spread 222ms)
REVIEW
Mean 119ms across 3 resolvers (spread 222ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 133ms
Got: 133ms via 8.8.8.8:53
Info::
Cloudflare: 223ms
Got: 223ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 222ms (min 1ms / max 223ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
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
TLS Certificate Expiry & Recommendations
43 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

43
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
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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
1 A records, 164 ms lookup
PASS
1 A records, 164 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 160.153.0.58
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: ns49.worldnic.com, ns50.worldnic.com
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: 164 ms
Got: 164 ms
A160.153.0.58
AAAA
CNAME
NSns49.worldnic.com, ns50.worldnic.com
MX
TXT
MS=ms31929728
CAALookup not available with standard resolver
Resolved in 164 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

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)

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://clinicsofnorthtexas.com/?utm_source=google&utm_medium=organic&utm_campaign=gbp

https://clinicsofnorthtexas.com/?utm_sou...

45 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://clinicsofnorthtexas.com/?utm_sou...20045 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 66 URLs
PASS
robots.txt present, sitemap with 66 URLs
Info::
robots.txt is present
Got: 511 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 66 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 511 B Sitemaps referenced 2 User-agents *, MJ12bot Blocking No — crawling allowed
# Robots.txt file generated by SEO Setup Plugin
# 2026-05-11 22:13:08

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /wp-login.php
Disallow: /wp-includes/
Disallow: /private/
Disallow: /cgi-bin/
Allow: /wp-content/uploads/
Allow: /wp-content/plugins/
Allow: /wp-content/themes/

# Block specific bots from certain paths
User-agent: MJ12bot
Disallow: /

# Sitemap URLs
Sitemap: https://clinicsofnorthtexas.com/sitemap.xml
Sitemap: https://clinicsofnorthtexas.com/image-sitemap.xml

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: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

301http://clinicsofnorthtexas.com/ https://clinicsofnorthtexas.com/

Consistent

A+
Domain Intelligence
clinicsofnorthtexas.com — via Network Solutions, LLC, 27 years, 5 months old, hosted on Cloudflare
PASS
clinicsofnorthtexas.com — via Network Solutions, LLC, 27 years, 5 months old, hosted on Cloudflare
Info::
Domain registered until Aug 10, 2031 (5 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: Network Solutions, 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: Cloudflare
Got: AS209242
Domain expiry

1810 days

August 10, 2031

SSL certificate

43 days

Issued by Google Trust Services

Domain age

27 years, 5 months

Registered August 10, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS209242

160.153.0.58

Registrar

Network Solutions, LLC

Unlocked 2 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 Network Solutions, LLC
Created August 10, 1999 (27 years, 5 months ago)
Expires August 10, 2031 (5 years)
Last Updated June 11, 2026
Name Servers ns49.worldnic.com, ns50.worldnic.com
DNSSEC Not enabled
Hosting
IP Address 160.153.0.58
ASN AS209242 (CLOUDFLARESPECTRUM - Cloudflare London, LLC, US)
Provider Cloudflare
Data source: rdap (0.4s)

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 403 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
141 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.
12 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
376 ms
Total Time Total request time from DNS lookup through full response.
403 ms

Connection waterfall

DNS Lookup 141 ms TCP Connect 1 ms TLS Handshake 12 ms Server Processing 223 ms Content Transfer 27 ms
A
CDN & Delivery
Cloudflare (MISS)
PASS
Cloudflare (MISS)
Info::
Site is served via Cloudflare CDN (edge: MAD)
Got: cf-ray: a30b22600c25f778-MAD
Info::
CDN cache status: MISS
CDN Detected: Cloudflare
Provider Cloudflare Cache Status MISS Evidence cf-ray: a30b22600c25f778-MAD
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=MISS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback