Skip to content
https://dental-ortho.info

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
F
HTTP Probe Timing
Action
Total 4353 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
586 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
277 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
281 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
3.52 s
Total Time Total request time from DNS lookup through full response.
4.35 s

Connection waterfall

DNS Lookup 586 ms TCP Connect 277 ms TLS Handshake 281 ms Server Processing 2.38 s Content Transfer 831 ms
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
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 219.94.128.182 does not match any cert SAN: www942.sakura.ne.jp
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 2403:3a00:101:9:219:94:128:182 does not match any cert SAN: www942.sakura.ne.jp
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 274ms across 3 resolvers (spread 18ms)
REVIEW
Mean 274ms across 3 resolvers (spread 18ms)
Info::
Quad9: 268ms
Got: 268ms via 9.9.9.9:53
Info::
Google: 269ms
Got: 269ms via 8.8.8.8:53
Info::
Cloudflare: 286ms
Got: 286ms via 1.1.1.1:53
B
TLS Certificate Expiry & Recommendations
51 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

51
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
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: connection error, /health: 404, /healthz: 404, /ping: connection error, /status: 404.
A
DNS Records
1 A records, 584 ms lookup
PASS
1 A records, 584 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 219.94.128.182
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2403:3a00:101:9:219:94:128:182
Info::
2 nameserver(s) configured
Got: ns1.dns.ne.jp, ns2.dns.ne.jp
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (584 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 584 ms
A219.94.128.182
AAAA2403:3a00:101:9:219:94:128:182
CNAME—
NSns1.dns.ne.jp, ns2.dns.ne.jp
MX
10 dental-ortho.info
TXT
SPF v=spf1 a:www942.sakura.ne.jp mx ~all
CAALookup not available with standard resolver
Resolved in 584 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

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+
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://dental-ortho.info

https://dental-ortho.info

3119 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dental-ortho.info2003119 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (265 ms)
PASS
IPv6 reachable (265 ms)
Info::
IPv6 is configured and reachable at 2403:3a00:101:9:219:94:128:182
Got: 265 ms connect
IPv6 Ready
AAAA Records 2403:3a00:101:9:219:94:128:182 Connection Reachable (265 ms)
A+
Crawlability
robots.txt present, sitemap with 3001 URLs
PASS
robots.txt present, sitemap with 3001 URLs
Info::
robots.txt is present
Got: 273 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3001 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 273 B Sitemaps referenced 5 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

sitemap: http://dental-ortho.info/sitemap727.xml

sitemap: http://dental-ortho.info/sitemap358.xml

sitemap: http://dental-ortho.info/sitemap273.xml

sitemap: http://dental-ortho.info/sitemap157.xml

sitemap: http://dental-ortho.info/sitemap323.xml
sitemap.xml 200 OK
Type URL Set URLs 3001 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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.dental-ortho.info/
200https://dental-ortho.info/

Preferred variant: non-www

HTTP → HTTPS

301http://dental-ortho.info/ → https://dental-ortho.info/

Consistent

A+
Domain Intelligence
dental-ortho.info — via GMO Internet Group, Inc. d/b/a Onamae.com, 4 years, 5 months old
PASS
dental-ortho.info — via GMO Internet Group, Inc. d/b/a Onamae.com, 4 years, 5 months old
Info::
Domain registered until Mar 14, 2027 (7 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: GMO Internet Group, Inc. d/b/a Onamae.com
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.
Domain expiry

217 days

March 14, 2027

SSL certificate

51 days

Issued by Let's Encrypt

Domain age

4 years, 5 months

Registered March 14, 2022

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2403:3a00:101:9:219:94:128:182

Registrar

GMO Internet Group, Inc. d/b/a Onamae.com

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 GMO Internet Group, Inc. d/b/a Onamae.com
Created March 14, 2022 (4 years, 5 months ago)
Expires March 14, 2027 (7 months)
Last Updated March 3, 2026
Name Servers ns1.dns.ne.jp, ns2.dns.ne.jp
DNSSEC Not enabled
Hosting
IP Address 2403:3a00:101:9:219:94:128:182
Data source: rdap (0.6s)

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