butikskassa.com

We performed a comprehensive analysis of butikskassa.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 26887ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 344 KB. 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 50/100 (moderate). The following security headers are properly configured: Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options. However, the site is missing 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 5 technologies across 5 categories powering butikskassa.com. The detected stack includes Vue.js, Google Tag Manager, Zendesk, Google Fonts, and jQuery 1.12.0.. The UI is built with Vue.js. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, butikskassa.com receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, butikskassa.com receives a trust score of 66/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. Areas of concern include: 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 butikskassa.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 butikskassa.com and identified 5 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. UI Library: Vue.js — handles the user interface rendering and component management for butikskassa.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for butikskassa.com. Support: Zendesk — handles customer support tickets and knowledge bases for butikskassa.com. Fonts: Google Fonts — delivers web fonts for typography for butikskassa.com. JavaScript Library: jQuery (version 1.12.0.) — provides utility functions and DOM manipulation for butikskassa.com. We also extracted the following tracking identifiers: Google Tag Manager container GTM-PK9774Z. These IDs can be used to identify other websites operated by the same organization.

butikskassa.com delivers its homepage in 26887ms (server response time), which is considered slow by industry standards. The total page weight is 344 KB, and we detected 301 resource requests loading assets from 9 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: 5 out of 6 CSS files and 8 out of 10 JavaScript files are minified. Minifying the remaining 3 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 butikskassa.com produces approximately 0.17g 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 344 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for butikskassa.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.

butikskassa.com resolves to the IPv4 address 52.28.249.62, 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 3 name servers: ns1.coreit.se, ns2.coreit.se, and ns3.coreit.se. Having 3 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 butikskassa.com is handled by azureit.se with 2 MX records configured: mx1.azureit.se and mx2.azureit.se. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 not enabled for butikskassa.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. Our subdomain enumeration scan discovered 2 active subdomains for butikskassa.com: support.butikskassa.com and www.butikskassa.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of butikskassa.com contains 1,490 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 14 H2 headings, 20 H3 headings, 0 H4 headings. The page includes 53 images. 40 images (75%) 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 25% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 202 internal links pointing to other pages on the same domain and 2 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 10 external JavaScript files, 6 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. We detected the following payment methods accepted on butikskassa.com: Visa and Klarna. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for butikskassa.com is well-optimized at 54 characters: "butikskassa.com | Etiketter, kassaregister & kassaskåp". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 152 characters (well-optimized): "Brett utbud av etikettskrivare, etiketter, kassasystem & kassaskåp! Välkommen in att bläddra i vårt sortiment. Kontakta ...". 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.butikskassa.com, preventing duplicate content issues, the page language is declared as sv, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("butikskassa.com | Etiketter, kassaregister & kassaskåp..."), 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.