actually-alice.com

We performed a comprehensive analysis of actually-alice.com on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 10203ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 613 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 0/100 (poor). No security headers are configured, which is a significant security concern. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 6 technologies across 6 categories powering actually-alice.com. The detected stack includes WordPress, Sentry, reCAPTCHA v3, Cloudflare, Google Fonts, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, actually-alice.com receives an overall trust score of 45/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, actually-alice.com receives a trust score of 45/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. 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, 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 actually-alice.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 actually-alice.com and identified 6 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. CMS: WordPress — manages the content and page structure for actually-alice.com. Monitoring: Sentry — monitors application performance and errors for actually-alice.com. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for actually-alice.com. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for actually-alice.com. Fonts: Google Fonts — delivers web fonts for typography for actually-alice.com. JavaScript Library: jQuery — provides utility functions and DOM manipulation for actually-alice.com.

actually-alice.com delivers its homepage in 10203ms (server response time), which is considered slow by industry standards. The total page weight is 613 KB, and we detected 390 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: 0 out of 12 CSS files and 1 out of 23 JavaScript files are minified. Minifying the remaining 34 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 actually-alice.com produces approximately 0.3g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 613 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for actually-alice.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.

actually-alice.com resolves to the IPv4 address 34.92.116.151, 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 2 name servers: a.share-dns.com and b.share-dns.net. 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. 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 actually-alice.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 25 active subdomains for actually-alice.com: admin.actually-alice.com, api.actually-alice.com, app.actually-alice.com, apps.actually-alice.com, blog.actually-alice.com, cdn.actually-alice.com, community.actually-alice.com, and dev.actually-alice.com. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of actually-alice.com contains 703 words of visible text content. This is a moderate amount of content. The page is structured with 49 H2 headings, 10 H3 headings, 0 H4 headings. The page includes 174 images. 77 images (44%) 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 56% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 63 internal links pointing to other pages on the same domain and 26 external links pointing to third-party websites. There are 23 external JavaScript files, 12 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Schema.org structured data (Article, EducationalOrganization, ImageObject, Organization, Person, SearchAction, WebPage, and WebSite) and RSS feed for content syndication. 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 actually-alice.com: Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.

The title tag for actually-alice.com is well-optimized at 57 characters: "168澳洲的幸运5彩票官网结果官方平台®2026最新澳洲的幸运5直播正规平台|168澳洲5彩票网_官方结果历史数据". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 121 characters (well-optimized): "168体彩网®澳洲幸运5彩票官网|澳洲五开奖结果历史记录 澳洲5幸运168中国福彩官网预测历史记录查询体彩 168澳洲5彩票网_官方结果历史数据 2026澳洲幸运5彩票官网预测结果+168开奖结果历史记录数据 澳洲5结果168预测计划记录 ...". 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 http://www.actually-alice.com/, preventing duplicate content issues, the page language is declared as en-gb, the meta robots directive is set to follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("168澳洲的幸运5彩票官网结果官方平台®2026最新澳洲的幸运5直播正规平台|168澳洲5彩票网_官方结果历史数据..."), OG description, 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: Article, EducationalOrganization, ImageObject, Organization, Person, SearchAction, WebPage, 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.