Skip to content
https://goodschina.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
3 PASS 4 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 404 Expected: 301 redirect to HTTPS

www / non-www

200https://www.goodschina.ru/
200https://goodschina.ru/

Inconsistent — duplicate content risk

HTTP → HTTPS

404http://goodschina.ru/

HTTP version does not redirect to HTTPS

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, 296 ms lookup
REVIEW
1 A records, 296 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 195.133.53.29
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: ns2.reg.ru, ns1.reg.ru
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
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 (296 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 296 ms
A195.133.53.29
AAAA
CNAME
NSns2.reg.ru, ns1.reg.ru
MX
TXT
CAALookup not available with standard resolver
Resolved in 296 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.

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

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
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 2649 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2649 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<!DOCTYPE html>
<html lang="en">

<head>
  <meta charset="UTF-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  <title>GOODS CHINA</title>
  <link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32" />
  <link rel="preconnect" href="https://knizgpullfdgeeueculf.supabase.co" crossorigin />
  <script>
    // Фикс F5 Chrome: патчим navigator.locks ДО загрузки любых модулей.
    // Supabase GoTrueClient вызывает navigator.locks.request синхронно в конструкторе —
    // патч в index.tsx всегда опаздывает, здесь — нет.
    if (navigator.locks) {
      try {
        Object.defineProperty(navigator, 'locks', {
          value: {
            request: function(name, optOrFn, fn) {
              var cb = typeof fn === 'function' ? fn : optOrFn;
              return Promise.resolve().then(function() { return cb({ name: name, mode: 'exclusive' }); });
            }
          },
          configurable: true,
          writable: true
        });
      } catch(e) {}
    }
  </script>
  <script>
    // Миграция ключа сессии: всегда используем ключ для прокси (sb-goodschina)
    (function() {
      var proxyKey = 'sb-goodschina-auth-token';
      var directKey = 'sb-knizgpullfdgeeueculf-auth-token';
      // Если есть ключ от прямого URL — переносим в ключ прокси
      var data = localStorage.getItem(directKey);
      if (data && !localStorage.getItem(proxyKey)) {
        localStorage.setItem(proxyKey, data);
        localStorage.removeItem(directKey);
      }
    })();
  </script>
  <script>
    (function() {
      var VERSION = "1.0.5";
      if (localStorage.getItem('app_version') !== VERSION) {
        var keys = Object.keys(localStorage);
        for (var i = 0; i < keys.length; i++) {
          if (keys[i] !== 'app_version') localStorage.removeItem(keys[i]);
        }
        localStorage.setItem('app_version', VERSION);
        window.location.reload();
      }
    })();
  </script>
  <!-- Google tag (gtag.js) -->
  <script async src="https://www.googletagmanager.com/gtag/js?id=G-2QRKGJB32X"></script>
  <script>
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());
    gtag('config', 'G-2QRKGJB32X');
  </script>
  <script type="module" crossorigin src="/assets/index-gKVK3eix.js"></script>
  <link rel="stylesheet" crossorigin href="/assets/index-BpDzux6U.css">
</head>

<body>
  <div id="root"></div>
</body>

</html>
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
61 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

61
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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://goodschina.ru

https://goodschina.ru

321 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://goodschina.ru200321 msHTTP/1.1nginx/1.24.0 (Ubuntu)
A+
Domain Intelligence
goodschina.ru — via REGRU-RU, 1 months old, hosted on ASBAXETN, RU
PASS
goodschina.ru — via REGRU-RU, 1 months old, hosted on ASBAXETN, RU
Info::
Domain registered until Mar 19, 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 Mar 19, 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: ASBAXETN, RU
Got: AS49392
Domain expiry

277 days

March 19, 2027

SSL certificate

61 days

Issued by Let's Encrypt

Domain age

1 months

Registered March 19, 2026

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ASBAXETN, RU

ASN AS49392

195.133.53.29

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 March 19, 2026 (1 months ago)
Expires March 19, 2027 (10 months)
Name Servers ns1.reg.ru, ns2.reg.ru
Hosting
IP Address 195.133.53.29
ASN AS49392 (ASBAXETN, RU)
Provider ASBAXETN, RU
Data source: whois (0.9s)

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

Connection waterfall

DNS Lookup 297 ms TCP Connect 104 ms TLS Handshake 111 ms Server Processing 106 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