aspiturf.com Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of aspiturf.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 3485ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 31 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 65/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-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 aspiturf.com. The detected stack includes Nuxt.js and React. The site uses Nuxt.js 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, aspiturf.com receives an overall trust score of 77/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time3485ms
ProtocolHTTP/1.1
Page Size31 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
ServerApache/2.4.58 (Ubuntu)
Total Requests19
3rd Party Domains1
RedirectNone
Detected Technologies (2)
🔧 Nuxt.js
⚛️ React
Security Headers
✗
Content-Security-Policy
Not set
✓
Strict-Transport-Security (HSTS)
Set ✓
✓
X-Content-Type-Options
Set ✓
✗
Permissions-Policy
Not set
SSL Certificate
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=YR1
SubjectcommonName=aspiturf.com
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
aspiturf.com Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, aspiturf.com receives a trust score of 77/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DNSSEC providing authenticated DNS responses.
Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved.
We checked aspiturf.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
✅ SPF configured
✅ DMARC configured (p=reject)
✅ DNSSEC enabled
✅ Sitemap.xml found
⚠️ Missing Content-Security-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
aspiturf.com Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned aspiturf.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.
Framework: Nuxt.js — provides the application framework and routing for aspiturf.com.
UI Library: React — handles the user interface rendering and component management for aspiturf.com.
Framework
UI Library
aspiturf.com Performance, Speed & Core Web Vitals
🤖 AI Summary
aspiturf.com delivers its homepage in 3485ms (server response time), which is considered slow by industry standards. The total page weight is 31 KB, and we detected 19 resource requests loading assets from 1 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 2 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 3 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 aspiturf.com produces approximately 0.02g 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 31 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for aspiturf.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.02g
RatingA
Page Weight & Optimization
HTML Size31 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests19
3rd Party Domains1
CSS Minified0/2
JS Minified0/1
aspiturf.com DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
aspiturf.com resolves to the IPv4 address 195.15.226.172, 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: ns41.infomaniak.com and ns42.infomaniak.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 aspiturf.com is handled by infomaniak.ch with 1 MX records configured: mta-gw.infomaniak.ch. 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 (Domain-based Message Authentication, Reporting and Conformance) is configured with a reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic.
DNSSEC is enabled for aspiturf.com, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites.
Our subdomain enumeration scan discovered 2 active subdomains for aspiturf.com: api.aspiturf.com and www.aspiturf.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns41.infomaniak.com
ns42.infomaniak.com
Email & Authentication
MX Providerinfomaniak.ch
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (2 found)
api.aspiturf.com www.aspiturf.com
aspiturf.com Page Content, Images & Accessibility
🤖 AI Summary
The homepage of aspiturf.com contains 20 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 1 image. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content).
The link structure consists of 0 internal links pointing to other pages on the same domain and 3 external links pointing to third-party websites. There are 1 external JavaScript files, 2 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).
Notable missing features: robots.txt and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
Content Structure
H1Courses du jour
H2 Tags0
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links0
External Links3
Assets & Features
JavaScript Files1
JS Minified0/1
CSS Files2
CSS Minified0/2
Iframes0
Images1
Missing Alt0
SitemapYes ✓
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
aspiturf.com SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
No meta description is configured for aspiturf.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 fr.
No Open Graph tags are configured. When someone shares a link to aspiturf.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.
Meta Tags
Title—...
Title Length0 chars
Meta Desc Length0 chars
H1Courses du jour
Languagefr
Canonical—
Meta Robotsnot set
Meta Keywordsnot set
Schema.org & Social
Schema Types—
OG Type—
OG ImageNot set
Twitter Card—
FaviconNot set