Skip to content
https://dyacys-l.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 10 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
Reverse DNS
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 141.125.104.208 does not match any cert SAN: d0.68.7d8d.ip4.static.sl-reverse.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 158.176.192.52 does not match any cert SAN: 34.c0.b09e.ip4.static.sl-reverse.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 141.125.157.19 does not match any cert SAN: 13.9d.7d8d.ip4.static.sl-reverse.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 158.176.188.102 does not match any cert SAN: 66.bc.b09e.ip4.static.sl-reverse.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
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 redirects to HTTPS permanently
Got: HTTP 308

www / non-www

200https://www.dyacys-l.com/
200https://dyacys-l.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://dyacys-l.com/ → https://dyacys-l.com/

Consistent

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

Connection waterfall

DNS Lookup 34 ms TCP Connect 28 ms TLS Handshake 61 ms Server Processing 1.05 s Content Transfer 36 ms
B
TLS Certificate Expiry & Recommendations
77 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

77
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 shop-themes-assets.ycdn.store, 130 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host shop-themes-assets.ycdn.store, 130 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (shop-themes-assets.ycdn.store, 130 assets), but the HTML document itself comes straight from the origin. 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: a54b112a8d9ea2e9-CDG
Info::
Assets on Cloudflare: shop-themes-assets.ycdn.store (assets: 130), cache HIT
Got: cf-ray: a54b112a8d9ea2e9-CDG
Info::
Assets on Cloudflare: assets.youcan.shop (assets: 45), cache HIT
Got: cf-ray: a54b112a7882d8d2-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • shop-themes-assets.ycdn.store — Cloudflare · assets: 130 · Cache Status: HIT
  • assets.youcan.shop — Cloudflare · assets: 45 · Cache Status: HIT

Other asset hosts

  • fonts.googleapis.com — assets: 2 · below probe threshold
  • img.youtube.com — assets: 1 · below probe threshold
  • static4.youcan.shop — assets: 1 · below probe threshold
  • unpkg.com — assets: 1 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold

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
4 A records, 36 ms lookup
PASS
4 A records, 36 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 141.125.104.208, 158.176.192.52, 141.125.157.19, 158.176.188.102
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.youcan.shop, ns2.youcan.shop
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 36 ms
Got: 36 ms
A141.125.104.208, 158.176.192.52, 141.125.157.19, 158.176.188.102
AAAA—
CNAME—
NSns1.youcan.shop, ns2.youcan.shop
MX
10 mx.zoho.eu
20 mx2.zoho.eu
50 mx3.zoho.eu
TXT
zoho-verification=zb06925070.zmverify.zoho.eu
SPF v=spf1 include:zohomail.eu include:youcan.shop ~all
CAALookup not available with standard resolver
Resolved in 36 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
CAA Records
issue: sectigo.com, digicert.com, letsencrypt.org, comodoca.com, amazon.com, pki.goog | issuewild: comodoca.com, sectigo.com, letsencrypt.org, pki.goog, digicert.com, amazon.com | iodef configured
PASS
issue: sectigo.com, digicert.com, letsencrypt.org, comodoca.com, amazon.com, pki.goog | issuewild: comodoca.com, sectigo.com, letsencrypt.org, pki.goog, digicert.com, amazon.com | iodef configured
Info::
CAA issue tag present — authorized CA(s): sectigo.com, digicert.com, letsencrypt.org, comodoca.com, amazon.com, pki.goog
Info::
CAA iodef tag present (failed-issuance notifications enabled)
A+
Multi-Resolver DNS Speed
Mean 27ms across 3 resolvers (spread 48ms)
PASS
Mean 27ms across 3 resolvers (spread 48ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 32ms
Got: 32ms via 8.8.8.8:53
Info::
Cloudflare: 49ms
Got: 49ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://dyacys-l.com

https://dyacys-l.com

1308 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dyacys-l.com2001308 msHTTP/1.1Youcan.Private.DC/2.0
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 25 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 25 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: * 
Disallow:
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
dyacys-l.com — via NameCheap, Inc., 12 days old, hosted on SOFTLAYER - IBM Cloud, US
PASS
dyacys-l.com — via NameCheap, Inc., 12 days old, hosted on SOFTLAYER - IBM Cloud, US
Info::
Domain registered until Oct 21, 2027 (11 months remaining)
Info::
Domain is only 12 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Oct 21, 2026
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: NameCheap, 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: SOFTLAYER - IBM Cloud, US
Got: AS36351
Domain expiry

347 days

October 21, 2027

SSL certificate

77 days

Issued by Let's Encrypt

Domain age

12 days

Registered October 21, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SOFTLAYER - IBM Cloud, US

ASN AS36351

158.176.192.52

Registrar

NameCheap, Inc.

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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameCheap, Inc.
Created October 21, 2026 (12 days ago)
Expires October 21, 2027 (11 months)
Last Updated October 21, 2026
Name Servers ns1.youcan.shop, ns2.youcan.shop
DNSSEC Not enabled
Hosting
IP Address 158.176.192.52
ASN AS36351 (SOFTLAYER - IBM Cloud, US)
Provider SOFTLAYER - IBM Cloud, US
Data source: rdap (0.4s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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