encar.store

We performed a comprehensive analysis of encar.store on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 1666ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 117 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-07-08, which is 8 days from now. The security headers analysis reveals a score of 15/100 (poor). The following security headers are properly configured: X-Frame-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, Referrer-Policy, and Permissions-Policy, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 2 technologies across 2 categories powering encar.store. The detected stack includes Google Fonts and jQuery 1.10.2.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, encar.store receives an overall trust score of 58/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, encar.store receives a trust score of 58/100, which places it in the "Caution Advised" category. This score is calculated by evaluating multiple factors including SSL certificate validity, domain registration history, email authentication protocols, security header configuration, and blacklist status across major threat intelligence databases. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit and a valid SSL certificate issued by Let's Encrypt with 8 days until expiration. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, missing Referrer-Policy, potentially leaking URL information to third parties, the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity, and DNSSEC is not enabled, leaving DNS queries vulnerable to spoofing attacks. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked encar.store against 8 major blacklist databases including Google Safe Browsing, Phishtank, Urlhaus, Openphish, Dnsfilter, Spamhaus Dbl, Surbl, and Virustotal. The domain passed all 8 checks with a clean status, meaning it has not been flagged for phishing, malware distribution, spam, or other malicious activities by any of the tested threat intelligence providers.

Our technology detection engine scanned encar.store and identified 2 distinct technologies across 2 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Fonts: Google Fonts — delivers web fonts for typography for encar.store. JavaScript Library: jQuery (version 1.10.2.) — provides utility functions and DOM manipulation for encar.store.

encar.store delivers its homepage in 1666ms (server response time), which is considered somewhat slow by industry standards. The total page weight is 117 KB, and we detected 79 resource requests loading assets from 11 third-party domains. A high number of third-party domains can significantly impact page load time due to additional DNS lookups and TLS handshakes required for each domain. The website uses Gzip compression for text-based assets, achieving an estimated 60.0% reduction in transfer size. This reduces bandwidth usage and improves page load times, especially for visitors on slower connections. Asset minification status: 10 out of 11 CSS files and 23 out of 23 JavaScript files are minified. Minifying the remaining 1 unminified file(s) could further reduce page weight by 10-30% for those assets. Minification is a best practice that reduces download sizes without affecting functionality. From an environmental perspective, each page view of encar.store produces approximately 0.06g of CO₂, earning a carbon rating of A. This places the website among the cleanest on the web, demonstrating efficient use of server resources and optimized content delivery. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 117 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for encar.store. This typically means the site doesn't have enough real-world Chrome user traffic to generate statistically significant field data, or the domain is not included in the CrUX dataset. Core Web Vitals (LCP, INP, CLS) are important Google ranking factors that measure real user experience.

encar.store resolves to the IPv4 address 185.215.4.59, but does not support IPv6. IPv6 adoption is increasingly important as IPv4 address space becomes exhausted, and some ISPs and regions are transitioning to IPv6-only connectivity. The domain has 1 A record(s) configured. The domain name system is managed by 2 name servers: ns1.reg.ru and ns2.reg.ru. Having 2 name servers provides good redundancy — if one fails, the others can continue serving DNS queries. The choice of name servers often indicates the DNS hosting provider or CDN service being used. SPF is not configured, meaning any server could potentially send emails pretending to be from this domain. This is a significant email security concern. DMARC is not configured, leaving the domain vulnerable to email spoofing and phishing attacks that impersonate this domain. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for encar.store. While not critical for most websites, DNSSEC adds an important security layer by ensuring DNS responses haven't been tampered with during transit. Enabling DNSSEC is recommended for domains handling sensitive data or financial transactions.

The homepage of encar.store contains 234 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 4 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 5 images. 5 images (100%) are missing alt text attributes, which is a significant concern for both accessibility and SEO. Screen readers rely on alt text to describe images to visually impaired users, and search engines use alt text to understand image content. Only 0% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 22 internal links pointing to other pages on the same domain and 6 external links pointing to third-party websites. There are 23 external JavaScript files, 11 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages) and robots.txt (controls search engine crawling behavior). Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. The website has social media presence across 2 platforms: Twitter (@s) and Youtube (@encarstore). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for encar.store is well-optimized at 54 characters: "Купить автомобиль из Южной Кореи с доставкой по России". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 255 characters (slightly long): "Купить проверенный автомобиль из Южной Кореи под ключ. От ведущего оператора Encar. Безналичная оплата и возможность офо...". Google typically displays up to 155-160 characters of the meta description in search results. A compelling meta description with a clear call-to-action can significantly improve click-through rates from search results. The canonical url is correctly set to http://encar.store/, preventing duplicate content issues and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Купить автомобиль из Южной Кореи с доставкой по России..."), OG description, OG image (social sharing thumbnail), OG type (website). These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. The meta keywords tag contains 1 terms including Автомобиль доставка в россию южная корея купить автомобиль из кореи купить автомобиль из кореи на заказ купить автомобиль из кореи Владивосток купить автомобиль с пробегом из кореи купить корейский автомобиль из кореи куплю автомобиль из кореи в России ку. Note: Google has officially confirmed that it does not use the meta keywords tag as a ranking signal. However, some other search engines (Bing, Yandex) may still reference it.