iplocation.io

We performed a comprehensive analysis of iplocation.io on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 7784ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 252 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-08-10, which is 41 days from now. The security headers analysis reveals a score of 30/100 (below average). The following security headers are properly configured: X-Frame-Options and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 7 technologies across 5 categories powering iplocation.io. The detected stack includes Bootstrap, Google Tag Manager, reCAPTCHA v3, Cloudflare Turnstile, Cloudflare, Fastly, and jQuery 3.3.1.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, iplocation.io receives an overall trust score of 75/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, iplocation.io receives a trust score of 75/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 41 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DNSSEC providing authenticated DNS responses. 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, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked iplocation.io 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 iplocation.io and identified 7 distinct technologies across 5 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CSS Framework: Bootstrap — provides the styling and responsive layout system for iplocation.io. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for iplocation.io. Security: reCAPTCHA v3 and Cloudflare Turnstile — provides security features like bot detection and CAPTCHA for iplocation.io. CDN: Cloudflare and Fastly — accelerates content delivery by caching assets at edge locations worldwide for iplocation.io. JavaScript Library: jQuery (version 3.3.1.) — provides utility functions and DOM manipulation for iplocation.io. We also extracted the following tracking identifiers: Google Tag Manager container GTM-M4GFP99. These IDs can be used to identify other websites operated by the same organization.

iplocation.io delivers its homepage in 7784ms (server response time), which is considered slow by industry standards. The total page weight is 252 KB, and we detected 163 resource requests loading assets from 14 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 4 CSS files and 2 out of 5 JavaScript files are minified. Minifying the remaining 6 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 iplocation.io produces approximately 0.12g 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 252 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for iplocation.io. 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.

iplocation.io resolves to the IPv4 address 104.26.10.222 and also supports IPv6 (2606:4700:20::681a:bde), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 2 name servers: eric.ns.cloudflare.com and gail.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 iplocation.io is handled by cloudflare.net with 3 MX records configured: isaac.mx.cloudflare.net, amir.mx.cloudflare.net, and linda.mx.cloudflare.net. 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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is enabled for iplocation.io, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. Our subdomain enumeration scan discovered 2 active subdomains for iplocation.io: api.iplocation.io and www.iplocation.io. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of iplocation.io contains 2,003 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 7 H2 headings, 5 H3 headings, 0 H4 headings, 9 H5, and 0 H6 headings. The page includes 3 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 124 internal links pointing to other pages on the same domain and 3 external links 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 5 external JavaScript files, 4 CSS stylesheets, and 1 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 title tag for iplocation.io is well-optimized at 52 characters: "IP Address Lookup - Check Location of Your Public IP". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 183 characters (slightly long): "IPLocation.io provides a free IP lookup tool to check the location of your IP Address. Data is gathered through several ...". 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://iplocation.io, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to follow, index, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("IP Address Lookup - Check Location of Your Public IP..."), 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. A Twitter Card of type summary is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type.