pos.pages.fm

We performed a comprehensive analysis of pos.pages.fm on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 31418ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 1080 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 35/100 (below average). The following security headers are properly configured: Content-Security-Policy and X-Frame-Options. However, the site is missing Strict-Transport-Security (HSTS), 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 7 technologies across 6 categories powering pos.pages.fm. The detected stack includes WooCommerce, Next.js chunks, React, Webpack, Vite, Shop Pay, and Google Fonts. The primary e-commerce platform is WooCommerce. The site uses Next.js as its primary framework (version chunks). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, pos.pages.fm receives an overall trust score of 58/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, pos.pages.fm receives a trust score of 58/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: a valid HTTPS connection protecting data in transit. 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 pos.pages.fm 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 pos.pages.fm and identified 7 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Ecommerce: WooCommerce — powers the online store and shopping functionality for pos.pages.fm. Framework: Next.js (version chunks) — provides the application framework and routing for pos.pages.fm. UI Library: React — handles the user interface rendering and component management for pos.pages.fm. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for pos.pages.fm. Payments: Shop Pay — processes payment transactions for pos.pages.fm. Fonts: Google Fonts — delivers web fonts for typography for pos.pages.fm.

pos.pages.fm resolves to the IPv4 address 113.20.119.56, 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. 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 pos.pages.fm. 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 pos.pages.fm: dev.pos.pages.fm and docs.pos.pages.fm. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The title tag for pos.pages.fm is well-optimized at 52 characters: "Pancake POS: Multi-channel Sales Management Software". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 165 characters (slightly long): "Streamline your sales with powerful multi-channel sales management software. Track inventory, manage orders, and boost p...". 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://pos.pancake.biz/, preventing duplicate content issues and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Pancake POS: Multi-channel Sales Management Software..."), 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. The meta keywords tag contains 9 terms including Pancake, Pancake POS, Pancake Global, POS Pancake, and POS. 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.