facialabusetube.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of facialabusetube.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 17438ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 139 KB, and the site is served behind a CDN (Content Delivery Network).
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 facialabusetube.com. The detected stack includes WordPress, Bootstrap, Google Analytics 4, Google Fonts, jQuery, and Font Awesome.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, facialabusetube.com receives an overall trust score of 56/100, classified as "Caution Advised".
HTTP Response
Status200 OK
Response Time17438ms
ProtocolHTTP/2
Page Size139 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests285
3rd Party Domains40
RedirectNone
Detected Technologies (6)
• WordPress
🎨 Bootstrap
📊 Google Analytics 4
🔤 Google Fonts
📦 jQuery
🎯 Font Awesome
Security Headers
✗
Content-Security-Policy
Not set
✗
Strict-Transport-Security (HSTS)
Not set
✗
X-Frame-Options
Not set
✗
X-Content-Type-Options
Not set
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=facialabusetube.com
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
facialabusetube.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, facialabusetube.com receives a trust score of 56/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 and SPF (Sender Policy Framework) email authentication preventing email spoofing.
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 facialabusetube.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.
Trust Signals
✅ Valid HTTPS
✅ SPF configured
⚠️ DNSSEC not enabled
✅ Sitemap.xml found
⚠️ Missing Content-Security-Policy
⚠️ Missing X-Frame-Options
⚠️ Missing Referrer-Policy
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
facialabusetube.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned facialabusetube.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 facialabusetube.com.
CSS Framework: Bootstrap — provides the styling and responsive layout system for facialabusetube.com.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for facialabusetube.com.
Fonts: Google Fonts — delivers web fonts for typography for facialabusetube.com.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for facialabusetube.com.
Icon Set: Font Awesome — provides additional functionality for facialabusetube.com.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-YMG2PSPSSM. These IDs can be used to identify other websites operated by the same organization.
CMS
CSS Framework
Analytics
📊 Google Analytics 4(95%)
Fonts
JavaScript Library
Icon Set
Tracking IDs
facialabusetube.com Performance, Speed & Core Web Vitals
🤖 AI Summary
facialabusetube.com delivers its homepage in 17438ms (server response time), which is considered slow by industry standards. The total page weight is 139 KB, and we detected 285 resource requests loading assets from 40 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: 3 out of 8 CSS files and 7 out of 19 JavaScript files are minified. Minifying the remaining 17 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.
The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors.
From an environmental perspective, each page view of facialabusetube.com produces approximately 0.07g 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 139 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for facialabusetube.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.
Core Web Vitals data not available
Requires CrUX API key configuration
Carbon Footprint
CO₂ per page view0.07g
RatingA
Page Weight & Optimization
HTML Size139 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests285
3rd Party Domains40
CSS Minified3/8
JS Minified7/19
facialabusetube.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
facialabusetube.com resolves to the IPv4 address 172.67.140.29 and also supports IPv6 (2606:4700:3031::ac43:8c1d), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured.
The domain name system is managed by 2 name servers: emma.ns.cloudflare.com and will.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.
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 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 facialabusetube.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 3 active subdomains for facialabusetube.com: dev.facialabusetube.com, mail.facialabusetube.com, and www.facialabusetube.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
172.67.140.29
104.21.73.41
AAAA
2606:4700:3031::ac43:8c1d
NS
emma.ns.cloudflare.com
will.ns.cloudflare.com
Email & Authentication
MX Provider—
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportYes ✓
Subdomains (3 found)
dev.facialabusetube.com mail.facialabusetube.com www.facialabusetube.com
facialabusetube.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of facialabusetube.com contains 1,635 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, 42 H3 headings, 7 H4 headings.
The page includes 41 images. 4 images (10%) 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 90% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 165 internal links pointing to other pages on the same domain and 30 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 19 external JavaScript files, 8 CSS stylesheets, and 0 iframes on the page.
The site implements the following web standards and features: XML Sitemap (helps search engines discover all pages), Schema.org structured data (WebPage and WebSite), and RSS feed for content syndication.
Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility.
Content Structure
H1—
H2 Tags0
H3 Tags42
H4 Tags7
H5 Tags0
H6 Tags0
Internal Links165
External Links30
Assets & Features
JavaScript Files19
JS Minified7/19
CSS Files8
CSS Minified3/8
Iframes0
Images41
Missing Alt4
SitemapYes ✓
Robots.txtNo
PWANo
AMPNo
RSS FeedYes ✓
Schema.org Types
facialabusetube.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for facialabusetube.com is well-optimized at 39 characters: "FacialAbuse Tube - Latest Video Updates". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation.
The meta description is 62 characters (acceptable): "Experience the latest facial abuse videos on FacialAbuse Tube.". 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://facialabusetube.com/, preventing duplicate content issues, the page language is declared as en-us, and the meta robots directive is set to max-image-preview:large.
Open Graph meta tags are configured with 4/4 recommended fields: OG title ("FacialAbuse Tube - Latest Video Updates..."), 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.
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: 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.
Google SERP Preview
FacialAbuse Tube - Latest Video Updates
https://facialabusetube.com
Experience the latest facial abuse videos on FacialAbuse Tube.
Meta Tags
TitleFacialAbuse Tube - Latest Video Updates...
Title Length39 chars
Meta Desc Length62 chars
H1—
Languageen-US
Canonicalhttps://facialabusetube.com/
Meta Robotsmax-image-preview:large
Meta Keywordsnot set
Schema.org & Social
Schema TypesWebPage, WebSite
OG Typewebsite
OG ImageSet ✓
Twitter Cardsummary_large_image
FaviconNot set
Open Graph Preview
facialabusetube.com
FacialAbuse Tube - Latest Video Updates
Experience the latest facial abuse videos on FacialAbuse Tube.
facialabusetube.com Related Domains & Cross-References
🤖 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 facialabusetube.com. 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: ga4_id: G-YMG2PSPSSM.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)