Skip to content
https://apcsro.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
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.

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
33 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

33
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
A+
DNS Records
1 A records, 129 ms lookup
PASS
1 A records, 129 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 45.130.41.153
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.com, ns1.beget.pro, ns2.beget.pro, ns1.beget.ru, ns2.beget.ru, ns1.beget.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 129 ms
Got: 129 ms
A45.130.41.153
AAAA
CNAME
NSns2.beget.com, ns1.beget.pro, ns2.beget.pro, ns1.beget.ru, ns2.beget.ru, ns1.beget.com
MX
10 mx1.beget.com
20 mx2.beget.com
TXT
SPF v=spf1 redirect=beget.com
CAALookup not available with standard resolver
Resolved in 129 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://apcsro.ru

https://apcsro.ru

308 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://apcsro.ru200308 msHTTP/1.1nginx-reuseport/1.21.1
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 80 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 80 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://apcsro.ru/sitemap.xml

Host: apcsro.ru

sitemap.xml 200 OK
Type URL Set URLs 1 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.apcsro.ru/
200https://apcsro.ru/

Preferred variant: non-www

HTTP → HTTPS

301http://apcsro.ru/ https://apcsro.ru/

Consistent

A+
Domain Intelligence
apcsro.ru — via BEGET-RU, 1 months old, hosted on BEGET-AS, RU
PASS
apcsro.ru — via BEGET-RU, 1 months old, hosted on BEGET-AS, RU
Info::
Domain registered until Feb 26, 2027 (10 months remaining)
Info::
Domain is only 1 months 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 Feb 26, 2026
Info::
Registrar: BEGET-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, RU
Got: AS198610
Domain expiry

258 days

February 26, 2027

SSL certificate

33 days

Issued by Let's Encrypt

Domain age

1 months

Registered February 26, 2026

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

BEGET-AS, RU

ASN AS198610

45.130.41.153

Registrar

BEGET-RU

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar BEGET-RU
Created February 26, 2026 (1 months ago)
Expires February 26, 2027 (10 months)
Name Servers ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro
Hosting
IP Address 45.130.41.153
ASN AS198610 (BEGET-AS, RU)
Provider BEGET-AS, RU
Data source: whois (0.7s)

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.

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

Connection waterfall

DNS Lookup 91 ms TCP Connect 74 ms TLS Handshake 77 ms Server Processing 149 ms Content Transfer 15 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback