runfox.com

We performed a comprehensive analysis of runfox.com on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 10973ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 57 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by ZeroSSL GmbH (DV type). The connection is encrypted using TLS 1.2 with the ECDHE-RSA-AES128-GCM-SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-08-06, which is 36 days from now. 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 2 technologies across 2 categories powering runfox.com. The detected stack includes Vue.js and jQuery. The UI is built with Vue.js. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, runfox.com receives an overall trust score of 60/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, runfox.com receives a trust score of 60/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, a valid SSL certificate issued by ZeroSSL GmbH with 36 days until expiration, and a well-established domain registered for over 14.4 years, indicating long-term commitment and legitimacy. 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 runfox.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. The domain is registered through GoDaddy.com, LLC based in CN, with a registration date of 2012-02-11 and expiration date of 2028-02-11.

Our technology detection engine scanned runfox.com and identified 2 distinct technologies across 2 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 runfox.com. JavaScript Library: jQuery — provides utility functions and DOM manipulation for runfox.com.

runfox.com delivers its homepage in 10973ms (server response time), which is considered slow by industry standards. The total page weight is 57 KB, and we detected 201 resource requests loading assets from 4 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. No compression is currently enabled on runfox.com. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 0 out of 3 CSS files and 3 out of 8 JavaScript files are minified. Minifying the remaining 8 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 runfox.com produces approximately 0.03g of CO₂, earning a carbon rating of A. 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 57 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for runfox.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.

runfox.com resolves to the IPv4 address 47.94.252.23, 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: ns3.dnsv2.com and ns4.dnsv2.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 runfox.com is handled by qq.com with 2 MX records configured: mxbiz1.qq.com and mxbiz2.qq.com. Multiple MX records provide failover redundancy — if the primary mail server is unavailable, email will be routed to the next available server. 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 runfox.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. The domain is registered through GoDaddy.com, LLC (CN). It was first registered on 2012-02-11 and is set to expire on 2028-02-11, making it 14.4 years old. Our subdomain enumeration scan discovered 10 active subdomains for runfox.com: admin.runfox.com, api.runfox.com, app.runfox.com, blog.runfox.com, cdn.runfox.com, dev.runfox.com, m.runfox.com, and mail.runfox.com. Plus 2 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of runfox.com contains 98 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 57 images. 46 images (81%) 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 19% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 8 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 8 external JavaScript files, 3 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. The website has social media presence across 1 platforms: Twitter (@gw). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for runfox.com is good at 17 characters: "小狐狸ABC_可以扮演的英文动画片". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 78 characters (well-optimized): "小狐狸ABC是一款神奇的、人人都可以用来学说英语的APP，它包含大量精彩原创故事，结合AI技术，让学习者与参与其中，通过对话驱动剧情，在情境中自然习得英语。". 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 page language is declared as en. No Open Graph tags are configured. When someone shares a link to runfox.com on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The meta keywords tag contains 11 terms including 小狐狸ABC官网, 小狐狸ABC下载, 小狐狸ABC怎么样, 小狐狸ABC多少钱, and 小狐狸ABC会员卡激活. 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.