cmcpart.com

We performed a comprehensive analysis of cmcpart.com on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 13871ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 213 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Asseco Data Systems S.A. (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2027-02-15, which is 230 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, X-Frame-Options, 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 cmcpart.com. The detected stack includes Nuxt.js and Vite. The site uses Nuxt.js as its primary framework. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, cmcpart.com receives an overall trust score of 56/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, cmcpart.com receives a trust score of 56/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: HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks and a valid SSL certificate issued by Asseco Data Systems S.A. with 230 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, no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 cmcpart.com 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 cmcpart.com 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. Framework: Nuxt.js — provides the application framework and routing for cmcpart.com. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for cmcpart.com.

cmcpart.com delivers its homepage in 13871ms (server response time), which is considered slow by industry standards. The total page weight is 213 KB, and we detected 187 resource requests loading assets from 21 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: 1 out of 7 CSS files and 0 out of 9 JavaScript files are minified. Minifying the remaining 15 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 cmcpart.com produces approximately 0.1g 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 213 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for cmcpart.com. 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.

cmcpart.com resolves to the IPv4 address 72.62.66.109, 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.julydns.com and ns2.julydns.com. 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 cmcpart.com. 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 cmcpart.com contains 844 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 65 images. 63 images (97%) 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 3% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 37 internal links pointing to other pages on the same domain and 58 external links pointing to third-party websites. There are 9 external JavaScript files, 7 CSS stylesheets, and 0 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on cmcpart.com: Discover and JCB. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates. The website has social media presence across 1 platforms: Github (@TP-Lab). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for cmcpart.com is too long at 294 characters: "TokenPocket - Your secure crypto & DeFi Wallet | TP wallet - ETH wallet - BTC wa...". At 294 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 175 characters (slightly long): "TokenPocket is a world-leading crypto wallet, supporting public blockchains including BTC, ETH, BSC, TRON, Aptos, Polygo...". 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. A favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("TokenPocket - Your secure crypto & DeFi Wallet | TP wallet -..."), OG description, 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 18 terms including TokenPocket, Token Pocket, TP wallet, Ethereum wallet, and Bitcoin. 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.