fencingtimelive.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of fencingtimelive.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 22586ms. The page is served over HTTP/2 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 10 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 70/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Content-Type-Options, and Referrer-Policy. However, the site is missing X-Frame-Options 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 7 technologies across 6 categories powering fencingtimelive.com. The detected stack includes Bootstrap 4.3.1, Google Analytics 4, Zendesk, Cloudflare, StackPath, jQuery 3.4.1., and Font Awesome.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, fencingtimelive.com receives an overall trust score of 70/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time22586ms
ProtocolHTTP/2
Page Size10 KB
CompressionNone
Compression SavingsN/A
CDNNo
Servernginx/1.30.2
Total Requests48
3rd Party Domains8
Redirect2 hop(s)
Detected Technologies (7)
🎨 Bootstrap
📊 Google Analytics 4
🎧 Zendesk
☁️ Cloudflare
☁️ StackPath
📦 jQuery
🎯 Font Awesome
Security Headers
✓
Content-Security-Policy
Set ✓
✓
Strict-Transport-Security (HSTS)
Set ✓
✗
X-Frame-Options
Not set
✓
X-Content-Type-Options
Set ✓
✗
Permissions-Policy
Not set
SSL Certificate
IssuerAmazon
Issuer FullcountryName=US, organizationName=Amazon, commonName=Amazon RSA 2048 M04
SubjectcommonName=*.fencingtimelive.com
Type—
TLS VersionTLS 1.2
Cipher SuiteECDHE-RSA-AES128-GCM-SHA256
Algorithm—
Issued—
Expires— (? days)
SANs—
fencingtimelive.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, fencingtimelive.com receives a trust score of 70/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 DMARC email authentication with a none policy.
Areas of concern include: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking), 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 fencingtimelive.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
✅ HSTS enabled
✅ DMARC configured (p=none)
⚠️ DNSSEC not enabled
✅ Robots.txt found
⚠️ Missing X-Frame-Options
Blacklist Checks (8/8 clean)
✓
Google Safe Browsing
clean
✓
Phishtank
clean
✓
Urlhaus
clean
✓
Openphish
clean
✓
Dnsfilter
clean
✓
Spamhaus Dbl
clean
✓
Surbl
clean
✓
Virustotal
clean
fencingtimelive.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned fencingtimelive.com and identified 7 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.
CSS Framework: Bootstrap (version 4.3.1) — provides the styling and responsive layout system for fencingtimelive.com.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for fencingtimelive.com.
Support: Zendesk — handles customer support tickets and knowledge bases for fencingtimelive.com.
CDN: Cloudflare and StackPath — accelerates content delivery by caching assets at edge locations worldwide for fencingtimelive.com.
JavaScript Library: jQuery (version 3.4.1.) — provides utility functions and DOM manipulation for fencingtimelive.com.
Icon Set: Font Awesome — provides additional functionality for fencingtimelive.com.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-VW57F97H1D. These IDs can be used to identify other websites operated by the same organization.
CSS Framework
Analytics
📊 Google Analytics 4(95%)
Support
CDN
☁️ Cloudflare(95%)☁️ StackPath(95%)
JavaScript Library
Icon Set
Tracking IDs
fencingtimelive.com Performance, Speed & Core Web Vitals
🤖 AI Summary
fencingtimelive.com delivers its homepage in 22586ms (server response time), which is considered slow by industry standards. The total page weight is 10 KB, and we detected 48 resource requests loading assets from 8 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 fencingtimelive.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: 6 out of 7 CSS files and 6 out of 9 JavaScript files are minified. Minifying the remaining 4 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 fencingtimelive.com produces approximately 0.0g 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 10 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for fencingtimelive.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.0g
RatingA
Page Weight & Optimization
HTML Size10 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests48
3rd Party Domains8
CSS Minified6/7
JS Minified6/9
fencingtimelive.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
fencingtimelive.com resolves to the IPv4 address 3.129.103.243, 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 3 A record(s) configured.
The domain name system is managed by 4 name servers: ns-1384.awsdns-45.org, ns-2013.awsdns-59.co.uk, ns-268.awsdns-33.com, and ns-914.awsdns-50.net. Having 4 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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. 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 fencingtimelive.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 24 active subdomains for fencingtimelive.com: admin.fencingtimelive.com, api.fencingtimelive.com, app.fencingtimelive.com, apps.fencingtimelive.com, blog.fencingtimelive.com, cdn.fencingtimelive.com, community.fencingtimelive.com, and dev.fencingtimelive.com. Plus 16 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
3.129.103.243
3.140.4.50
3.140.33.155
NS
ns-1384.awsdns-45.org
ns-2013.awsdns-59.co.uk
ns-268.awsdns-33.com
ns-914.awsdns-50.net
Email & Authentication
MX Provider—
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (24 found)
admin.fencingtimelive.com api.fencingtimelive.com app.fencingtimelive.com apps.fencingtimelive.com blog.fencingtimelive.com cdn.fencingtimelive.com community.fencingtimelive.com dev.fencingtimelive.com developers.fencingtimelive.com docs.fencingtimelive.com ftp.fencingtimelive.com help.fencingtimelive.com m.fencingtimelive.com partners.fencingtimelive.com portal.fencingtimelive.com shop.fencingtimelive.com smtp.fencingtimelive.com staging.fencingtimelive.com static.fencingtimelive.com status.fencingtimelive.com store.fencingtimelive.com support.fencingtimelive.com webmail.fencingtimelive.com www.fencingtimelive.com
fencingtimelive.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of fencingtimelive.com contains 100 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 3 images. 3 images (100%) 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 0% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 24 internal links pointing to other pages on the same domain and 4 external links pointing to third-party websites. There are 9 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).
Notable missing features: XML Sitemap and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
Content Structure
H1—
H2 Tags0
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links24
External Links4
Assets & Features
JavaScript Files9
JS Minified6/9
CSS Files7
CSS Minified6/7
Iframes0
Images3
Missing Alt3
SitemapNo
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedNo
fencingtimelive.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for fencingtimelive.com is good at 17 characters: "Fencing Time Live". The length is acceptable, though it may be slightly truncated in some search result displays.
The meta description is 25 characters (acceptable): "Fencing Time Live Results". 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.
A favicon is configured.
Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Fencing Time Live..."), 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.
Google SERP Preview
Fencing Time Live
https://fencingtimelive.com
Fencing Time Live Results
Meta Tags
TitleFencing Time Live...
Title Length17 chars
Meta Desc Length25 chars
H1—
Language—
Canonical—
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Typewebsite
OG ImageSet ✓
Twitter Card—
FaviconSet ✓
Open Graph Preview
fencingtimelive.com
Fencing Time Live
Fencing Time Live Results
fencingtimelive.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 fencingtimelive.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-VW57F97H1D.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)