Infrastructure - https://studioglass.ua/?srsltid=AfmBOorR_9oMrvnyWn3YEJOwuhmKA3daecu2_JGxPxX23K

F

HTTP Probe Timing

Action

Total 3147 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

FIX

DNS Lookup

1 ms

TCP Connect

57 ms

TLS Handshake

62 ms

Time to First Byte

3.15 s

Total Time

3.15 s

Connection waterfall

DNS Lookup 1 ms TCP Connect 57 ms TLS Handshake 62 ms Server Processing 3.03 s Content Transfer 1 ms

D

CDN & Delivery

Action

No CDN detected

FIX

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)

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)

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

PTR for 185.67.3.250 does not match any cert SAN: 185.67.3.250.hostpro.com.ua

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

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

129 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

129

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

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

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

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, 2 ms lookup

PASS

1 A records, 2 ms lookup

Resolves to 1 IPv4 address(es)

Got: 185.67.3.250

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

12 nameserver(s) configured

Got: nsb1.srv53.org, nsa2.srv53.org, nsc4.srv53.net, nsd3.srv53.net, nsc1.srv53.org, nsc3.srv53.com, nsd4.srv53.com, nsb2.srv53.com, nsd2.srv53.org, nsa4.srv53.net, nsb3.srv53.net, nsa1.srv53.com

1 mail exchanger(s) configured

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 2 ms

Got: 2 ms

A	185.67.3.250
AAAA	—
CNAME	—
NS	nsb1.srv53.org, nsa2.srv53.org, nsc4.srv53.net, nsd3.srv53.net, nsc1.srv53.org, nsc3.srv53.com, nsd4.srv53.com, nsb2.srv53.com, nsd2.srv53.org, nsa4.srv53.net, nsb3.srv53.net, nsa1.srv53.com
MX	0 mx.imena.ua
TXT	google-site-verification=_TssH0mwWwYlp7QE3SXnnyjrfpdPCnsAnNmcgxrhnvQ
CAA	Lookup not available with standard resolver

Resolved in 2 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

No CNAME record present

A

Multi-Resolver DNS Speed

Mean 33ms across 3 resolvers (spread 72ms)

PASS

Mean 33ms across 3 resolvers (spread 72ms)

Quad9: 0ms

Got: 0ms via 9.9.9.9:53

Google: 27ms

Got: 27ms via 8.8.8.8:53

Cloudflare: 72ms

Got: 72ms via 1.1.1.1:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://studioglass.ua/?srsltid=AfmBOorR_9oMrvnyWn3YEJOwuhmKA3daecu2_JGxPxX23K_k9dm-TCQT

https://studioglass.ua/?srsltid=AfmBOorR...

680 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://studioglass.ua/?srsltid=AfmBOorR...	200	680 ms	HTTP/1.1	nginx

A+

Crawlability

robots.txt present, sitemap with 640 URLs

PASS

robots.txt present, sitemap with 640 URLs

robots.txt is present

Got: 187 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 640 entries

robots.txt references sitemap

robots.txt 200 OK

Size 187 B Sitemaps referenced 1 User-agents Googlebot-image, Googlebot Blocking No — crawling allowed

User-agent: Googlebot
Disallow: /auth
Disallow: /configurator
User-agent: Googlebot-image
Disallow: /auth
Disallow: /configurator
Disallow: /?

Sitemap: https://studioglass.ua/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 640 entries Valid XML Yes

Sample URLs:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

301https://www.studioglass.ua/

200https://studioglass.ua/

Preferred variant: non-www

HTTP → HTTPS

301http://studioglass.ua/ → https://studioglass.ua/

Consistent

A

Domain Intelligence

studioglass.ua — via Internet Invest LLC, 9 years, 11 months old, hosted on HOSTPRO-AS - HOSTPRO LAB LLC, UA

PASS

studioglass.ua — via Internet Invest LLC, 9 years, 11 months old, hosted on HOSTPRO-AS - HOSTPRO LAB LLC, UA

Domain expires in 81 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Nov 14, 2026

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.

Registrar: Internet Invest LLC

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.

Hosting: HOSTPRO-AS - HOSTPRO LAB LLC, UA

Got: AS196645

Domain expiry

80 days

November 14, 2026

SSL certificate

129 days

Issued by Sectigo Limited

Domain age

9 years, 11 months

Registered November 14, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

HOSTPRO-AS - HOSTPRO LAB LLC, UA

ASN AS196645

185.67.3.250

Registrar

Internet Invest LLC

Unlocked 12 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 Internet Invest LLC

Created November 14, 2016 (9 years, 11 months ago)

Expires November 14, 2026 (2 months)

Last Updated October 17, 2025

Name Servers nsa1.srv53.com, nsa2.srv53.org, nsa4.srv53.net, nsb1.srv53.org, nsb2.srv53.com, nsb3.srv53.net, nsc1.srv53.org, nsc3.srv53.com, nsc4.srv53.net, nsd2.srv53.org, nsd3.srv53.net, nsd4.srv53.com

DNSSEC Not enabled

Registrant not published

Hosting

IP Address 185.67.3.250

ASN AS196645 (HOSTPRO-AS - HOSTPRO LAB LLC, UA)

Provider HOSTPRO-AS - HOSTPRO LAB LLC, UA

Data source: rdap (0.3s)

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