fenoxo.com

HTTPS HTTP/2 HSTS Gzip WordPress Angular Crawled in 75,351ms · June 27, 2026 19:00 UTC

fenoxo.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of fenoxo.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 29696ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 80 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 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, 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 5 technologies across 5 categories powering fenoxo.com. The detected stack includes WordPress 5.7.15, Angular, React, jQuery, and Font Awesome. The site uses Angular as its primary framework. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, fenoxo.com receives an overall trust score of 60/100, classified as "Likely Safe".
60
/ 100
Trust Score
20
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time29696ms
ProtocolHTTP/2
Page Size80 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Servernginx/1.19.10
Total Requests316
3rd Party Domains13
Redirect1 hop(s)
Detected Technologies (5)
• WordPress 🔧 Angular ⚛️ React 📦 jQuery 🎯 Font Awesome
Security Headers
Content-Security-Policy
Not set
Strict-Transport-Security (HSTS)
Set ✓
X-Frame-Options
Not set
X-Content-Type-Options
Not set
Referrer-Policy
Not set
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=R13
SubjectcommonName=fenoxo.com
Type
TLS VersionTLS 1.2
Cipher SuiteECDHE-RSA-AES256-GCM-SHA384
Algorithm
Issued
Expires— (? days)
SANs

fenoxo.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, fenoxo.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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, 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 fenoxo.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.
60
/ 100
Likely Safe
Trust Signals
Valid HTTPS
HSTS enabled
SPF configured
⚠️ DNSSEC not enabled
Robots.txt 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

fenoxo.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned fenoxo.com and identified 5 distinct technologies across 5 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 (version 5.7.15) — manages the content and page structure for fenoxo.com. Framework: Angular — provides the application framework and routing for fenoxo.com. UI Library: React — handles the user interface rendering and component management for fenoxo.com. JavaScript Library: jQuery — provides utility functions and DOM manipulation for fenoxo.com. Icon Set: Font Awesome — provides additional functionality for fenoxo.com.
CMS
• WordPress 5.7.15(100%)
Framework
🔧 Angular(95%)
UI Library
⚛️ React(95%)
JavaScript Library
📦 jQuery(95%)
Icon Set
🎯 Font Awesome(95%)

fenoxo.com Performance, Speed & Core Web Vitals

🤖 AI Summary
fenoxo.com delivers its homepage in 29696ms (server response time), which is considered slow by industry standards. The total page weight is 80 KB, and we detected 316 resource requests loading assets from 13 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 7 CSS files and 5 out of 7 JavaScript files are minified. Minifying the remaining 6 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 fenoxo.com produces approximately 0.04g 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 80 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for fenoxo.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.04g
RatingA
Page Weight & Optimization
HTML Size80 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests316
3rd Party Domains13
CSS Minified3/7
JS Minified5/7

fenoxo.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
fenoxo.com resolves to the IPv4 address 144.217.255.197, 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: eva.ns.cloudflare.com and jim.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 fenoxo.com is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 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 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 fenoxo.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 1 active subdomains for fenoxo.com: www.fenoxo.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
144.217.255.197
NS
eva.ns.cloudflare.com
jim.ns.cloudflare.com
MX
aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
aspmx2.googlemail.com
aspmx3.googlemail.com
Email & Authentication
SPF
DMARC p=—
DKIM
DNSSEC
MX ProviderGoogle Workspace
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportNo
Subdomains (1 found)
www.fenoxo.com

fenoxo.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of fenoxo.com contains 5,334 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, 16 H3 headings, 0 H4 headings. The page includes 12 images. 11 images (92%) 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 8% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 237 internal links pointing to other pages on the same domain and 40 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 7 external JavaScript files, 7 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and RSS feed for content syndication. Notable missing features: XML Sitemap 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 (@art_moira). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
5,334
Words
12
Images
8%
Alt Text Score
80
Page Size (KB)
Content Structure
H1Fenoxo's Blog
H2 Tags0
H3 Tags16
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links237
External Links40
Assets & Features
JavaScript Files7
JS Minified5/7
CSS Files7
CSS Minified3/7
Iframes0
Images12
Missing Alt11
SitemapNo
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedYes ✓
Social Media Presence
Twitter: @art_moira

fenoxo.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for fenoxo.com is well-optimized at 38 characters: "Fenoxo's Blog – Home of NSFW Ramblings". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. No meta description is configured for fenoxo.com. This is a critical SEO oversight — without a meta description, Google will auto-generate a snippet from page content, which may not accurately represent the page or entice users to click. Adding a unique, compelling meta description of 120-155 characters is strongly recommended. The page language is declared as en-us, the meta robots directive is set to max-image-preview:large, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to fenoxo.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.
Google SERP Preview
Fenoxo's Blog – Home of NSFW Ramblings
https://fenoxo.com
Meta Tags
TitleFenoxo's Blog – Home of NSFW Ramblings...
Title Length38 chars
Meta Desc Length0 chars
H1Fenoxo's Blog
Languageen-US
Canonical
Meta Robotsmax-image-preview:large
Meta Keywordsnot set
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconSet ✓