Skip to content
https://master-220v.ru

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
7
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 7 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 218ms across 3 resolvers (spread 534ms)
FIX
Mean 218ms across 3 resolvers (spread 534ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 118ms
Got: 118ms via 8.8.8.8:53
Info::
Cloudflare: 535ms
Got: 535ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 534ms (min 1ms / max 535ms)
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.
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

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
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 31.28.24.244 does not match any cert SAN: sni0.hoster.ru
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
TLS Certificate Expiry & Recommendations
60 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

60
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
1 A records, 82 ms lookup
PASS
1 A records, 82 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 31.28.24.244
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: ns10.hoster.ru, ns11.hoster.ru
Info::
1 mail exchanger(s) configured
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: 82 ms
Got: 82 ms
A31.28.24.244
AAAA—
CNAME—
NSns10.hoster.ru, ns11.hoster.ru
MX
10 mxs.hoster.ru
TXT—
CAALookup not available with standard resolver
Resolved in 82 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
CAA Records
issue: letsencrypt.org
PASS
issue: letsencrypt.org
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://master-220v.ru

https://master-220v.ru

319 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://master-220v.ru200319 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 28 URLs
PASS
robots.txt present, sitemap with 28 URLs
Info::
robots.txt is present
Got: 293 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 28 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 293 B Sitemaps referenced 1 User-agents *, Yandex, Siteliner Blocking No — crawling allowed
User-Agent: *

Allow: /

Disallow: /index.php?page=$

Disallow: /index.php?page=zgt

Host: https://master-220v.ru
User-Agent: Yandex

Allow: /

Disallow: /index.php?page=$

Disallow: /index.php?page=zgt

Allow: /

User-agent: Siteliner

Allow: /

Sitemap: https://master-220v.ru/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 28 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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.master-220v.ru/
200https://master-220v.ru/

Preferred variant: non-www

HTTP → HTTPS

301http://master-220v.ru/ → https://master-220v.ru/

Consistent

A+
Domain Intelligence
master-220v.ru — via DOMENUS-RU, 2 years, 11 months old, hosted on CITYTELECOM-AS - Citytelecom LLC, RU
PASS
master-220v.ru — via DOMENUS-RU, 2 years, 11 months old, hosted on CITYTELECOM-AS - Citytelecom LLC, RU
Info::
Domain registered until Nov 4, 2027 (1 years, 1 months remaining)
Info::
Registrar: DOMENUS-RU
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: CITYTELECOM-AS - Citytelecom LLC, RU
Got: AS29076
Domain expiry

381 days

November 4, 2027

SSL certificate

60 days

Issued by Let's Encrypt

Domain age

2 years, 11 months

Registered November 4, 2023

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CITYTELECOM-AS - Citytelecom LLC, RU

ASN AS29076

31.28.24.244

Registrar

DOMENUS-RU

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar DOMENUS-RU
Created November 4, 2023 (2 years, 11 months ago)
Expires November 4, 2027 (1 years, 1 months)
Name Servers ns10.hoster.ru, ns11.hoster.ru
Hosting
IP Address 31.28.24.244
ASN AS29076 (CITYTELECOM-AS - Citytelecom LLC, RU)
Provider CITYTELECOM-AS - Citytelecom LLC, RU
Data source: whois (1.0s)

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

Connection waterfall

DNS Lookup 121 ms TCP Connect 65 ms TLS Handshake 157 ms Server Processing 93 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback