ip.cc

We performed a comprehensive analysis of ip.cc on 2026-06-29. The website returned an HTTP 200 status code with a server response time of 11853ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 330 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Google Trust Services (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_256_GCM_SHA384 cipher suite and ECDSA-SHA256 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-09-23, which is 86 days from now. The security headers analysis reveals a score of 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 4 technologies across 4 categories powering ip.cc. The detected stack includes Nuxt.js, React, Tailwind CSS, and Cloudflare. The site uses Nuxt.js as its primary framework. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ip.cc receives an overall trust score of 63/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, ip.cc receives a trust score of 63/100, which places it in the "Likely Safe" 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, a valid SSL certificate issued by Google Trust Services with 86 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and a well-established domain registered for over 28.7 years, indicating long-term commitment and legitimacy. 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 ip.cc 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. The domain is registered through Alibaba Cloud Computing (Beijing) Co., Ltd. based in CA, with a registration date of 1997-10-13 and expiration date of 2030-03-26.

Our technology detection engine scanned ip.cc and identified 4 distinct technologies across 4 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 ip.cc. UI Library: React — handles the user interface rendering and component management for ip.cc. CSS Framework: Tailwind CSS — provides the styling and responsive layout system for ip.cc. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for ip.cc.

ip.cc delivers its homepage in 11853ms (server response time), which is considered slow by industry standards. The total page weight is 330 KB, and we detected 394 resource requests loading assets from 3 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 15 CSS files and 1 out of 3 JavaScript files are minified. Minifying the remaining 16 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. The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors. From an environmental perspective, each page view of ip.cc produces approximately 0.16g of CO₂, earning a carbon rating of B. 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 330 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ip.cc. 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.

ip.cc resolves to the IPv4 address 172.67.151.6, 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 2 A record(s) configured. The domain name system is managed by 2 name servers: dorthy.ns.cloudflare.com and jay.ns.cloudflare.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. Email for ip.cc is handled by mxhichina.com with 2 MX records configured: mxn.mxhichina.com and mxw.mxhichina.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. SPF (Sender Policy Framework) is configured, which specifies which mail servers are authorized to send email on behalf of this domain. This helps prevent email spoofing and improves email deliverability. 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 ip.cc. 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 domain is registered through Alibaba Cloud Computing (Beijing) Co., Ltd. (CA). It was first registered on 1997-10-13 and is set to expire on 2030-03-26, making it 28.7 years old. Our subdomain enumeration scan discovered 3 active subdomains for ip.cc: api.ip.cc, mail.ip.cc, and www.ip.cc. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of ip.cc contains 1,870 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 3 H2 headings, 2 H3 headings, 0 H4 headings. The page includes 145 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 161 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 3 external JavaScript files, 15 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), robots.txt (controls search engine crawling behavior), and Schema.org structured data (AggregateRating, Person, Product, Rating, and Review).

The title tag for ip.cc is too long at 79 characters: "IP.CC - Professional IP Information Lookup and IP Address Data Provider - IP.CC". At 79 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 166 characters (slightly long): "IP.CC provides professional IP information lookup services with precise IP address data for businesses. Used for user an...". 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 https://ip.cc/, preventing duplicate content issues, the page language is declared as en-us, and a favicon is configured. Open Graph meta tags are configured with 2/4 recommended fields: OG title ("IP.CC - Professional IP Information Lookup and IP Address Da..."), OG description, These tags control how the page appears when shared on Facebook, LinkedIn, and other social media platforms that support the Open Graph protocol. The site implements Schema.org structured data with the following types: AggregateRating, Person, Product, Rating, and Review. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates. The meta keywords tag contains 3 terms including IP information, IP information look up, and IP address. 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.