Skip to content
https://coachmentor.ru

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
9
PASS
6
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
6 PASS 9 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 208ms across 3 resolvers (spread 338ms)
FIX
Mean 208ms across 3 resolvers (spread 338ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 280ms
Got: 280ms via 8.8.8.8:53
Info::
Quad9: 342ms
Got: 342ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 338ms (min 4ms / max 342ms)
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
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 87.236.16.25 does not match any cert SAN: ssl.aramis.beget.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

C
HTTP Probe Timing
Action
Total 1943 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
872 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
202 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
207 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.90 s
Total Time Total request time from DNS lookup through full response.
1.94 s

Connection waterfall

DNS Lookup 872 ms TCP Connect 202 ms TLS Handshake 207 ms Server Processing 617 ms Content Transfer 44 ms
B
TLS Certificate Expiry & Recommendations
48 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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: 404, /health: 404, /healthz: 404, /ping: 503, /status: 404.
A
DNS Records
1 A records, 567 ms lookup
PASS
1 A records, 567 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 87.236.16.25
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns2.beget.ru, ns1.beget.ru, ns2.beget.pro, ns1.beget.pro, ns2.beget.com, ns1.beget.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (567 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 567 ms
A87.236.16.25
AAAA—
CNAME—
NSns2.beget.ru, ns1.beget.ru, ns2.beget.pro, ns1.beget.pro, ns2.beget.com, ns1.beget.com
MX
10 mx1.beget.com
20 mx2.beget.com
TXT
SPF v=spf1 include:beget.com include:spf.unisender.com ~all
CAALookup not available with standard resolver
Resolved in 567 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://coachmentor.ru

https://coachmentor.ru

1473 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://coachmentor.ru2001473 msHTTP/1.1nginx-reuseport/1.21.1
A+
Crawlability
robots.txt present, sitemap with 11 URLs
PASS
robots.txt present, sitemap with 11 URLs
Info::
robots.txt is present
Got: 172 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11 entries
Info::
Sitemap index with 11 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 172 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://coachmentor.ru/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 11 entries Valid XML Yes
Child Sitemaps:
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.coachmentor.ru/
200https://coachmentor.ru/

Preferred variant: non-www

HTTP → HTTPS

301http://coachmentor.ru/ → https://coachmentor.ru/

Consistent

A+
Domain Intelligence
coachmentor.ru — via REGRU-RU, 6 years, 9 months old, hosted on BEGET-AS - Beget LLC, RU
PASS
coachmentor.ru — via REGRU-RU, 6 years, 9 months old, hosted on BEGET-AS - Beget LLC, RU
Info::
Domain registered until Jan 13, 2027 (3 months remaining)
Info::
Registrar: REGRU-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: BEGET-AS - Beget LLC, RU
Got: AS198610
Domain expiry

114 days

January 13, 2027

SSL certificate

48 days

Issued by Let's Encrypt

Domain age

6 years, 9 months

Registered January 13, 2020

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

BEGET-AS - Beget LLC, RU

ASN AS198610

87.236.16.25

Registrar

REGRU-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 REGRU-RU
Created January 13, 2020 (6 years, 9 months ago)
Expires January 13, 2027 (3 months)
Name Servers ns1.beget.com, ns2.beget.com
Hosting
IP Address 87.236.16.25
ASN AS198610 (BEGET-AS - Beget LLC, RU)
Provider BEGET-AS - Beget LLC, RU
Data source: whois (1.8s)

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