aafo.com

HTTPS HTTP/1.1 Crawled in 24,275ms · June 27, 2026 16:48 UTC

aafo.com Website Overview & Technology Report

🤖 AI Summary
We performed a comprehensive analysis of aafo.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 6174ms. 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 41 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 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 1 technologies across 1 categories powering aafo.com. The detected stack includes Google AdSense. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, aafo.com receives an overall trust score of 53/100, classified as "Caution Advised".
53
/ 100
Trust Score
0
/ 100
Security Headers
HTTP Response
Status200 OK
Response Time6174ms
ProtocolHTTP/1.1
Page Size41 KB
CompressionNone
Compression SavingsN/A
CDNNo
ServerApache
Total Requests112
3rd Party Domains8
RedirectNone
Detected Technologies (1)
📢 Google AdSense
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
IssuerLet's Encrypt
Issuer FullcountryName=US, organizationName=Let's Encrypt, commonName=R13
SubjectcommonName=www.aafo.com
Type
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm
Issued
Expires— (? days)
SANs

aafo.com Trust Score & Safety Analysis

🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, aafo.com receives a trust score of 53/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. 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 aafo.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.
53
/ 100
Caution Advised
Trust Signals
Valid HTTPS
⚠️ 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

aafo.com Technology Stack & Detected Technologies

🤖 AI Summary
Our technology detection engine scanned aafo.com and identified 1 distinct technologies across 1 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for aafo.com.
Advertising
📢 Google AdSense(95%)

aafo.com Performance, Speed & Core Web Vitals

🤖 AI Summary
aafo.com delivers its homepage in 6174ms (server response time), which is considered slow by industry standards. The total page weight is 41 KB, and we detected 112 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 aafo.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 0 CSS files and 0 out of 5 JavaScript files are minified. Minifying the remaining 5 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 aafo.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 41 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for aafo.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 Size41 KB
CompressionNone
Compression SavingsN/A
CDNNo
Total Requests112
3rd Party Domains8
CSS Minified0/0
JS Minified0/5

aafo.com DNS Records, Email Authentication & Domain Registration

🤖 AI Summary
aafo.com resolves to the IPv4 address 74.50.74.210, 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 3 name servers: cdns1.interserver.net, cdns2.interserver.net, and cdns3.interserver.net. Having 3 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 aafo.com is handled by aafo.com with 1 MX records configured: mail.aafo.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 aafo.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 aafo.com: www.aafo.com. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
74.50.74.210
NS
cdns1.interserver.net
cdns2.interserver.net
cdns3.interserver.net
MX
mail.aafo.com
Email & Authentication
SPF
DMARC p=—
DKIM
DNSSEC
MX Provideraafo.com
Registrar
Organisation
Country
Contact
Registered
Expires
Domain Age
IPv6 SupportNo
Subdomains (1 found)
www.aafo.com

aafo.com Page Content, Images & Accessibility

🤖 AI Summary
The homepage of aafo.com contains 803 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 38 images. 33 images (87%) 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 13% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 49 internal links pointing to other pages on the same domain and 8 external links pointing to third-party websites. There are 5 external JavaScript files, 0 CSS stylesheets, and 1 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.
803
Words
38
Images
13%
Alt Text Score
41
Page Size (KB)
Content Structure
H1
H2 Tags0
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links49
External Links8
Assets & Features
JavaScript Files5
JS Minified0/5
CSS Files0
CSS Minified0/0
Iframes1
Images38
Missing Alt33
SitemapNo
Robots.txtYes ✓
PWANo
AMPNo
RSS FeedNo

aafo.com SEO Analysis, Meta Tags & Open Graph

🤖 AI Summary
The title tag for aafo.com is too long at 72 characters: "Reno Air Races Aviation Photography and Airshow News Vacation At Casinos". At 72 characters, the title will likely be truncated in Google search results (recommended: 50-60 characters). Consider shortening it while keeping the most important keywords at the beginning. The meta description is 136 characters (well-optimized): "Las Vegas Air Show Reno Air Races Digital aviation photography humor Pilot profiles video and audio interviews plane pic...". 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 meta robots directive is set to index,follow. No Open Graph tags are configured. When someone shares a link to aafo.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 62 terms including Las Vegas, Arizona, travel, digital photography, and reno air races. 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.
Google SERP Preview
Reno Air Races Aviation Photography and Airshow News Vacation At Casinos
https://aafo.com
Las Vegas Air Show Reno Air Races Digital aviation photography humor Pilot profiles video and audio interviews plane pictures at Oshkosh
Meta Tags
TitleReno Air Races Aviation Photography and Airshow News Vacatio...
Title Length72 chars
Meta Desc Length136 chars
H1
Language
Canonical
Meta Robotsindex,follow
Meta KeywordsLas Vegas, Arizona, travel, digital photography, reno air ra...
Schema.org & Social
Schema Types
OG Type
OG ImageNot set
Twitter Card
FaviconNot set