Skip to content
https://apprestore.ru

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
12
PASS
4
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
4 PASS 12 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 (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
1 A records, 460 ms lookup
REVIEW
1 A records, 460 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 (460 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 460 ms
A161.104.32.46
AAAA—
CNAME—
NSns1.reg.ru, ns2.reg.ru
MX—
TXT
yandex-verification: 74a9dc7dd7ffe021
fk-verify=edf093a4edc4eedb871d8ec726af7555
brevo-code:93750a5bf257908a525dfce91a2adeba
google-site-verification=4ZGHgqd-8v1VIKkUgb-kQJB7kwt16_MEgNqRcV2u1yQ
CAALookup not available with standard resolver
Resolved in 460 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
Multi-Resolver DNS Speed
Action
Mean 175ms across 3 resolvers (spread 264ms)
REVIEW
Mean 175ms across 3 resolvers (spread 264ms)
Info::
Cloudflare: 5ms
Got: 5ms via 1.1.1.1:53
Info::
Quad9: 253ms
Got: 253ms via 9.9.9.9:53
Info::
Google: 269ms
Got: 269ms via 8.8.8.8:53
Info::
High latency spread between resolvers: 264ms (min 5ms / max 269ms)
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.
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.apprestore.ru/
200https://apprestore.ru/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
HTTP Probe Timing
Total 1024 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
445 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
191 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
196 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.02 s
Total Time Total request time from DNS lookup through full response.
1.02 s

Connection waterfall

DNS Lookup 445 ms TCP Connect 191 ms TLS Handshake 196 ms Server Processing 192 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
82 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

82
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.
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: 404, /status: 404.
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://apprestore.ru

https://apprestore.ru

1003 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://apprestore.ru2001003 msHTTP/1.1nginx/1.24.0 (Ubuntu)
A+
Crawlability
robots.txt present, sitemap with 122 URLs
PASS
robots.txt present, sitemap with 122 URLs
Info::
robots.txt is present
Got: 189 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 122 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 189 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /api/
Disallow: /pay/
Disallow: /o/
Disallow: /install/
Disallow: /recover
Disallow: /payment/
Disallow: /admin

Sitemap: https://apprestore.ru/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 122 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
apprestore.ru — via REGRU-RU, 7 days old, hosted on SELECTEL-MSK - JSC Selectel, RU
PASS
apprestore.ru — via REGRU-RU, 7 days old, hosted on SELECTEL-MSK - JSC Selectel, RU
Info::
Domain registered until Aug 31, 2027 (11 months remaining)
Info::
Domain is only 7 days 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 Aug 31, 2026
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

353 days

August 31, 2027

SSL certificate

82 days

Issued by Let's Encrypt

Domain age

7 days

Registered August 31, 2026

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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar REGRU-RU
Created August 31, 2026 (7 days ago)
Expires August 31, 2027 (11 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 (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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback