Skip to content
https://ark-russia.ru

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
9
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
6 PASS 9 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 246ms across 3 resolvers (spread 473ms)
FIX
Mean 246ms across 3 resolvers (spread 473ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Quad9: 262ms
Got: 262ms via 9.9.9.9:53
Info::
Google: 475ms
Got: 475ms via 8.8.8.8:53
Info::
High latency spread between resolvers: 473ms (min 2ms / max 475ms)
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 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.

B
DNS Records
1 A records, 597 ms lookup
REVIEW
1 A records, 597 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 161.104.32.46
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: ns1.reg.ru, ns2.reg.ru
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (597 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 597 ms
A161.104.32.46
AAAA—
CNAME—
NSns1.reg.ru, ns2.reg.ru
MX—
TXT
yandex-verification: bea7c3b01a0916f5
google-site-verification=EwdgnnX4yj64X7cX4wyM8nb8vCRQbvPuJW-Ooy-C-Zk
CAALookup not available with standard resolver
Resolved in 597 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)

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

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.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 161.104.32.46: lookup 161.104.32.46: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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
HTTP Probe Timing
Total 1441 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
736 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
229 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
236 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.44 s
Total Time Total request time from DNS lookup through full response.
1.44 s

Connection waterfall

DNS Lookup 736 ms TCP Connect 229 ms TLS Handshake 236 ms Server Processing 239 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
77 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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.
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://ark-russia.ru

https://ark-russia.ru

1293 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ark-russia.ru2001293 msHTTP/1.1nginx/1.24.0 (Ubuntu)
A+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 189 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 189 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /admin
Disallow: /api/
Sitemap: https://ark-russia.ru/sitemap.xml
Sitemap: https://ark-russia.ru/image-sitemap.xml
LLMs-txt: https://ark-russia.ru/llms.txt
sitemap.xml 200 OK
Type Sitemap Index URLs 4 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 301-redirects to HTTPS

www / non-www

301https://www.ark-russia.ru/
200https://ark-russia.ru/

Preferred variant: non-www

HTTP → HTTPS

301http://ark-russia.ru/ → https://ark-russia.ru/

Consistent

A+
Domain Intelligence
ark-russia.ru — via REGRU-RU, 8 years, 4 months old, hosted on SELECTEL-MSK - JSC Selectel, RU
PASS
ark-russia.ru — via REGRU-RU, 8 years, 4 months old, hosted on SELECTEL-MSK - JSC Selectel, RU
Info::
Domain registered until Apr 29, 2027 (9 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: SELECTEL-MSK - JSC Selectel, RU
Got: AS50340
Domain expiry

276 days

April 29, 2027

SSL certificate

77 days

Issued by Let's Encrypt

Domain age

8 years, 4 months

Registered April 29, 2018

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

SELECTEL-MSK - JSC Selectel, RU

ASN AS50340

161.104.32.46

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 April 29, 2018 (8 years, 4 months ago)
Expires April 29, 2027 (9 months)
Name Servers ns1.reg.ru, ns2.reg.ru
Hosting
IP Address 161.104.32.46
ASN AS50340 (SELECTEL-MSK - JSC Selectel, RU)
Provider SELECTEL-MSK - JSC Selectel, RU
Data source: whois (2.2s)

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+
Health Check Endpoint
Health endpoint at https://ark-russia.ru/health (HTTP 200)
PASS
Health endpoint at https://ark-russia.ru/health (HTTP 200)
Info::
Public health endpoint at https://ark-russia.ru/health
Got: https://ark-russia.ru/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback