apecon.ru Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of apecon.ru on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 13932ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 89 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 apecon.ru. The detected stack includes Google Analytics 4.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, apecon.ru receives an overall trust score of 61/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time13932ms
ProtocolHTTP/2
Page Size89 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Servernginx
Total Requests123
3rd Party Domains9
RedirectNone
Detected Technologies (1)
📊 Google Analytics 4
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=*.apecon.ru
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
apecon.ru Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, apecon.ru receives a trust score of 61/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a none policy, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification.
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 apecon.ru 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
✅ DMARC configured (p=none)
✅ DKIM configured
⚠️ DNSSEC not enabled
✅ Sitemap.xml found
✅ 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
apecon.ru Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned apecon.ru 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.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for apecon.ru.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-P2M2Y0C2V7. These IDs can be used to identify other websites operated by the same organization.
Analytics
📊 Google Analytics 4(95%)
Tracking IDs
apecon.ru Performance, Speed & Core Web Vitals
🤖 AI Summary
apecon.ru delivers its homepage in 13932ms (server response time), which is considered slow by industry standards. The total page weight is 89 KB, and we detected 123 resource requests loading assets from 9 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 0 CSS files and 0 out of 3 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 apecon.ru 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 89 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for apecon.ru. 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 Size89 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests123
3rd Party Domains9
CSS Minified0/0
JS Minified0/3
apecon.ru DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
apecon.ru resolves to the IPv4 address 35.214.141.30, 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: ns1.siteground.net and ns2.siteground.net. 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 apecon.ru is handled by mailspamprotection.com with 3 MX records configured: mx10.mailspamprotection.com, mx20.mailspamprotection.com, and mx30.mailspamprotection.com. 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 none policy — a monitoring-only setting that doesn't enforce any action on unauthorized emails. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit.
DNSSEC is not enabled for apecon.ru. 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 4 active subdomains for apecon.ru: ftp.apecon.ru, mail.apecon.ru, webmail.apecon.ru, and www.apecon.ru. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns1.siteground.net
ns2.siteground.net
MX
mx10.mailspamprotection.com
mx20.mailspamprotection.com
mx30.mailspamprotection.com
Email & Authentication
MX Providermailspamprotection.com
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (4 found)
ftp.apecon.ru mail.apecon.ru webmail.apecon.ru www.apecon.ru
apecon.ru Page Content, Images & Accessibility
🤖 AI Summary
The homepage of apecon.ru contains 2,707 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 3 H2 headings, 1 H3 headings, 0 H4 headings.
The page includes 9 images. 1 images (11%) 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 89% of images have proper alt text — we recommend adding descriptive alt attributes to all images.
The link structure consists of 94 internal links pointing to other pages on the same domain and 4 external links pointing to third-party websites. There are 3 external JavaScript files, 0 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), robots.txt (controls search engine crawling behavior), and Progressive Web App (PWA) manifest (enabling app-like installation).
Notable missing features: Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.
Content Structure
H1ПРОГНОЗ КУРСА ДОЛЛАРА НА МЕСЯЦ, 2026, 2027-2030 ГОДЫ
H2 Tags3
H3 Tags1
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links94
External Links4
Assets & Features
JavaScript Files3
JS Minified0/3
CSS Files0
CSS Minified0/0
Iframes0
Images9
Missing Alt1
SitemapYes ✓
Robots.txtYes ✓
PWAYes ✓
AMPNo
RSS FeedNo
apecon.ru SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for apecon.ru is well-optimized at 52 characters: "ПРОГНОЗ КУРСА ДОЛЛАРА НА МЕСЯЦ, 2026, 2027-2030 ГОДЫ". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation.
The meta description is 189 characters (slightly long): "Прогноз курса доллара на завтра, неделю, месяц от экспертов. Прогноз курса доллара на 2026, 2027, 2028, 2029 и 2030 годы...". 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://apecon.ru, preventing duplicate content issues, the page language is declared as ru-ru, and a favicon is configured.
Open Graph meta tags are configured with 4/4 recommended fields: OG title ("ПРОГНОЗ КУРСА ДОЛЛАРА НА МЕСЯЦ, 2026, 2027-2030 ГОДЫ..."), OG description, OG image (social sharing thumbnail), OG type (article). 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 is configured, which controls how links appear when shared on Twitter/X. The "summary" type displays a large image preview, which typically generates higher engagement rates than the basic card type.
The meta keywords tag contains 4 terms including прогноз доллара к рублю, курс Доллар-Рубль прогноз, курс доллара к рублю сегодня, and конвертер валют USD-RUB. 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
ПРОГНОЗ КУРСА ДОЛЛАРА НА МЕСЯЦ, 2026, 2027-2030 ГОДЫ
https://apecon.ru
Прогноз курса доллара на завтра, неделю, месяц от экспертов. Прогноз курса доллара на 2026, 2027, 2028, 2029 и 2030 годы на каждый месяц. Курс доллара сегодня. Конвертер валют Доллар-Рубль.
Meta Tags
TitleПРОГНОЗ КУРСА ДОЛЛАРА НА МЕСЯЦ, 2026, 2027-2030 ГОДЫ...
Title Length52 chars
Meta Desc Length189 chars
H1ПРОГНОЗ КУРСА ДОЛЛАРА НА МЕСЯЦ, 2026, 2027-2030 ГОДЫ
Languageru-RU
Canonicalhttps://apecon.ru
Meta Robotsnot set
Meta Keywordsпрогноз доллара к рублю, курс Доллар-Рубль прогноз, курс дол...
Schema.org & Social
Schema Types—
OG Typearticle
OG ImageSet ✓
Twitter Cardsummary
FaviconSet ✓
Open Graph Preview
apecon.ru
ПРОГНОЗ КУРСА ДОЛЛАРА НА МЕСЯЦ, 2026, 2027-2030 ГОДЫ
Прогноз курса доллара на завтра, неделю, месяц от экспертов. Прогноз курса доллара на 2026, 2027, 2028, 2029 и 2030 годы на каждый месяц. Курс доллара сегодня.
apecon.ru 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 apecon.ru. 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-P2M2Y0C2V7.
Tracking IDs for Cross-Referencing
Related Domains
Related domain data requires database (populated after batch crawl)