pages.fm

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, pages.fm receives a trust score of 72/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, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. Areas of concern include: 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 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.

🤖 AI Summary

Our technology detection engine scanned pages.fm and identified 3 distinct technologies across 3 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: React — handles the user interface rendering and component management for pages.fm. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for pages.fm. Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for pages.fm. We also extracted the following tracking identifiers: Meta (Facebook) Pixel ID 474959831926506. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

pages.fm delivers its homepage in 9214ms (server response time), which is considered slow by industry standards. The total page weight is 508 KB, and we detected 199 resource requests loading assets from 20 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 0 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 1 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 pages.fm produces approximately 0.25g 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 508 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for pages.fm. 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.

🤖 AI Summary

pages.fm resolves to the IPv4 address 113.20.119.46, 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 4 A record(s) configured. The domain name system is managed by 2 name servers: max.ns.cloudflare.com and olga.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 pages.fm is handled by pancake.vn with 6 MX records configured: mail.pancake.vn, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 3 more. 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 not enabled for 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 4 active subdomains for pages.fm: blog.pages.fm, dev.pages.fm, docs.pages.fm, and www.pages.fm. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of pages.fm contains 1,942 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 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 102 images. 1 images (1%) 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 99% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 59 internal links pointing to other pages on the same domain and 22 external links pointing to third-party websites. There are 1 external JavaScript files, 0 CSS stylesheets, and 0 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility. We detected the following payment methods accepted on pages.fm: JCB. 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 1 platforms: Facebook (@tr). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for pages.fm is well-optimized at 52 characters: "Pancake | The All-in-One Business Messaging Platform". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 190 characters (slightly long): "Kết nối mọi cuộc trò chuyện, giao dịch và dữ liệu khách hàng trên một nền tảng duy nhất. Đơn giản hóa quy trình quản lý ...". 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://pancake.biz/, preventing duplicate content issues, the page language is declared as vi, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Pancake: Nền tảng quản lý hội thoại đa kênh toàn diện..."), 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 3 terms including Pancake, Pancake v2, and Phần mềm quản lý FanPage. 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.

🤖 AI Summary

Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with pages.fm. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: meta_pixel_id: 474959831926506.

🤖 AI Summary

This section shows additional intelligence about pages.fm including data breach history (via HaveIBeenPwned), web archive history (Wayback Machine), green/eco-friendly hosting status, and mobile app presence in the iOS App Store.