HomeDirectory Cchange.com

change.com

HTTPS HTTP/2 HSTS Gzip Cloudflare Next.js Crawled in 18,084ms · June 27, 2026 14:50 UTC

change.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of change.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 5294ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 405 KB, and the site is served behind a CDN (Content Delivery Network). Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. 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 9 technologies across 8 categories powering change.com. The detected stack includes Next.js media, Webpack, Vite, Google Analytics 4, Google Tag Manager, Zendesk, Cloudflare, Google Fonts, and WP Rocket. The site uses Next.js as its primary framework (version media). Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, change.com receives an overall trust score of 69/100, classified as "Likely Safe".
69
/ 100
Trust Score
20
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time5294ms
ProtocolHTTP/2
Page Size405 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests318
3rd Party Domains14
Redirect3 hop(s)
Detected Technologies (9)
🔧 Next.js 🔨 Webpack 🔨 Vite 📊 Google Analytics 4 🏷️ Google Tag Manager 🎧 Zendesk ☁️ Cloudflare 🔤 Google Fonts ⚡ WP Rocket
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Set ✓
X-Frame-Options
Not set
X-Content-Type-Options
Not set
Referrer-Policy
Not set
Permissions-Policy
Not set
SSL Certificate
IssuerGoDaddy.com, Inc.
Issuer FullcountryName=US, stateOrProvinceName=Arizona, localityName=Scottsdale, organizationName=GoDaddy.com, Inc., organizationalUnitName=http://certs.godaddy.com/repository/, commonName=Go Daddy Secure Certificate Authority - G2
SubjectcommonName=*.change.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

change.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, change.com receives a trust score of 69/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, DKIM (DomainKeys Identified Mail) providing cryptographic email verification, 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, 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, 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 change.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.
69
/ 100
Likely Safe
Trust Signals
Valid HTTPS
HSTS enabled
SPF configured
DMARC configured (p=reject)
DKIM configured
DNSSEC enabled
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
Google Safe Browsing clean
Phishtank clean
Urlhaus clean
Openphish clean
Dnsfilter clean
Spamhaus Dbl clean
Surbl clean
Virustotal clean

change.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned change.com and identified 9 distinct technologies across 8 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version media) — provides the application framework and routing for change.com. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for change.com. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for change.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for change.com. Support: Zendesk — handles customer support tickets and knowledge bases for change.com. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for change.com. Fonts: Google Fonts — delivers web fonts for typography for change.com. Performance: WP Rocket — optimizes page loading speed and performance for change.com. We also extracted the following tracking identifiers: Google Tag Manager container GTM-5M23V5C. These IDs can be used to identify other websites operated by the same organization.
Framework
🔧 Next.js media(100%)
Build Tool
🔨 Webpack(95%)🔨 Vite(95%)
Analytics
📊 Google Analytics 4(95%)
Tag Manager
🏷️ Google Tag Manager(95%)
Support
🎧 Zendesk(95%)
CDN
☁️ Cloudflare(100%)
Fonts
🔤 Google Fonts(95%)
Performance
⚡ WP Rocket(95%)
Tracking IDs
gtm_idGTM-5M23V5C

change.com Performance, Speed & Core Web Vitals

🤖 AI Summary
change.com delivers its homepage in 5294ms (server response time), which is considered slow by industry standards. The total page weight is 405 KB, and we detected 318 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: 0 out of 2 CSS files and 1 out of 25 JavaScript files are minified. Minifying the remaining 26 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 change.com produces approximately 0.2g 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 405 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for change.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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.2g
RatingB
Page Weight & Optimization
HTML Size405 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests318
3rd Party Domains14
CSS Minified0/2
JS Minified1/25

change.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
change.com resolves to the IPv4 address 104.20.46.71 and also supports IPv6 (2606:4700:10::ac42:92fc), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: megan.ns.cloudflare.com and terin.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 change.com is handled by Microsoft 365 with 1 MX records configured: change-com.o-v1.mx.microsoft. 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 (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is enabled for change.com, 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 4 active subdomains for change.com: help.change.com, mail.change.com, shop.change.com, and www.change.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
104.20.46.71
172.66.146.252
AAAA
2606:4700:10::ac42:92fc
NS
megan.ns.cloudflare.com
terin.ns.cloudflare.com
MX
change-com.o-v1.mx.microsoft
Email & Authentication
SPF
DMARC p=reject
DKIM
DNSSEC
MX ProviderMicrosoft 365
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportYes ✓
Subdomains (4 found)
help.change.com mail.change.com shop.change.com www.change.com

change.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of change.com contains 596 words of visible text content. This is a moderate amount of content. The page is structured with 31 H2 headings, 5 H3 headings, 0 H4 headings. The page includes 93 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 158 internal links pointing to other pages on the same domain and 16 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 25 external JavaScript files, 2 CSS stylesheets, and 1 iframes on the page. The site implements the following web standards and features: Schema.org structured data (ContactPoint, Organization, PostalAddress, SearchAction, and WebSite). Notable missing features: XML Sitemap and robots.txt. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on change.com: Visa, Mastercard, Discover, and Klarna. 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 5 platforms: Facebook (@changedanmark), Instagram (@changelingerie), Linkedin (@change-of-scandinavia), Youtube (@ChangeLingerie), and Tiktok (@changelingerie_). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
596
Words
93
Images
100%
Alt Text Score
405
Page Size (KB)
Content Structure
H1
H2 Tags31
H3 Tags5
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links158
External Links16
Assets & Features
JavaScript Files25
JS Minified1/25
CSS Files2
CSS Minified0/2
Iframes1
Images93
Missing Alt0
SitemapNo
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Schema.org Types
ContactPointOrganizationPostalAddressSearchActionWebSite
Payment Methods Detected
💳 Visa💳 Mastercard💳 Discover💳 Klarna
Social Media Presence
Facebook: @changedanmarkInstagram: @changelingerieLinkedin: @change-of-scandinaviaYoutube: @ChangeLingerieTiktok: @changelingerie_

change.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for change.com is good at 67 characters: "Twilfit by CHANGE | Bh:ar, trosor, badkläder, natt- och loungeplagg". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 192 characters (slightly long): "Kolla in vår nya kollektion av damunderkläder, underkläder och nattkläder. Gå med i Club CHANGE, där vi har mer än 2 mil...". 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://www.change.com/se, preventing duplicate content issues and the page language is declared as sv. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Twilfit by CHANGE | Bh:ar, trosor, badkläder, natt- och loun..."), 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_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type. The site implements Schema.org structured data with the following types: ContactPoint, Organization, PostalAddress, SearchAction, and WebSite. 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.
Google SERP Preview
Twilfit by CHANGE | Bh:ar, trosor, badkläder, natt- och loungeplagg
https://change.com
Kolla in vår nya kollektion av damunderkläder, underkläder och nattkläder. Gå med i Club CHANGE, där vi har mer än 2 miljoner medlemmar över hela Europa som delar vår passion för underkläder.
Meta Tags
TitleTwilfit by CHANGE | Bh:ar, trosor, badkläder, natt- och loun...
Title Length67 chars
Meta Desc Length192 chars
H1
Languagesv
Canonicalhttps://www.change.com/se
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema TypesContactPoint, Organization, PostalAddress, SearchAction, WebSite
OG Typewebsite
OG ImageSet ✓
Twitter Cardsummary_large_image
FaviconNot set
Open Graph Preview
change.com
Twilfit by CHANGE | Bh:ar, trosor, badkläder, natt- och loungeplagg
Kolla in vår nya kollektion av damunderkläder, underkläder och nattkläder. Gå med i Club CHANGE, där vi har mer än 2 miljoner medlemmar över hela Europa som del