astrodata.bg Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of astrodata.bg on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 8306ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 30 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 5 technologies across 4 categories powering astrodata.bg. The detected stack includes Google Analytics 4, Meta Pixel, Google AdSense, reCAPTCHA v3, and jQuery.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, astrodata.bg receives an overall trust score of 58/100, classified as "Caution Advised".
HTTP Response
Status200 OK
Response Time8306ms
ProtocolHTTP/2
Page Size30 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
ServerApache
Total Requests141
3rd Party Domains14
RedirectNone
Detected Technologies (5)
📊 Google Analytics 4
📢 Meta Pixel
📢 Google AdSense
🔒 reCAPTCHA v3
📦 jQuery
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=astrodata.bg
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
astrodata.bg Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, astrodata.bg receives a trust score of 58/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, 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 astrodata.bg 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
✅ DKIM configured
⚠️ DNSSEC not enabled
✅ Sitemap.xml 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
astrodata.bg Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned astrodata.bg and identified 5 distinct technologies across 4 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 astrodata.bg.
Advertising: Meta Pixel and Google AdSense — handles advertising pixel tracking and conversion measurement for astrodata.bg.
Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for astrodata.bg.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for astrodata.bg.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-84V249J3HR and Meta (Facebook) Pixel ID 300899700433414. These IDs can be used to identify other websites operated by the same organization.
Analytics
📊 Google Analytics 4(95%)
Advertising
📢 Meta Pixel(95%)📢 Google AdSense(95%)
Security
JavaScript Library
Tracking IDs
ga4_idG-84V249J3HR
meta_pixel_id300899700433414
astrodata.bg Performance, Speed & Core Web Vitals
🤖 AI Summary
astrodata.bg delivers its homepage in 8306ms (server response time), which is considered slow by industry standards. The total page weight is 30 KB, and we detected 141 resource requests loading assets from 14 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 3 CSS files and 0 out of 10 JavaScript files are minified. Minifying the remaining 13 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 astrodata.bg produces approximately 0.01g 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 30 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for astrodata.bg. 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.01g
RatingA
Page Weight & Optimization
HTML Size30 KB
CompressionGzip
Compression Savings~60.0%
CDNNo
Total Requests141
3rd Party Domains14
CSS Minified0/3
JS Minified0/10
astrodata.bg DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
astrodata.bg resolves to the IPv4 address 91.196.125.100, 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: ns47.superhosting.bg and ns48.superhosting.bg. 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 astrodata.bg is handled by astrodata.bg with 1 MX records configured: astrodata.bg. 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 (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 astrodata.bg. 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 6 active subdomains for astrodata.bg: ftp.astrodata.bg, m.astrodata.bg, mail.astrodata.bg, smtp.astrodata.bg, webmail.astrodata.bg, and www.astrodata.bg. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
NS
ns47.superhosting.bg
ns48.superhosting.bg
Email & Authentication
MX Providerastrodata.bg
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportNo
Subdomains (6 found)
ftp.astrodata.bg m.astrodata.bg mail.astrodata.bg smtp.astrodata.bg webmail.astrodata.bg www.astrodata.bg
astrodata.bg Page Content, Images & Accessibility
🤖 AI Summary
The homepage of astrodata.bg contains 166 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 85 internal links pointing to other pages on the same domain and 5 external links pointing to third-party websites. There are 10 external JavaScript files, 3 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.
The website has social media presence across 2 platforms: Facebook (@horoskopite) and Twitter (@astrodatabg). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1—
H2 Tags0
H3 Tags0
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links85
External Links5
Assets & Features
JavaScript Files10
JS Minified0/10
CSS Files3
CSS Minified0/3
Iframes0
Images3
Missing Alt3
SitemapYes ✓
Robots.txtNo
PWANo
AMPNo
RSS FeedNo
Social Media Presence
Facebook: @horoskopiteTwitter: @astrodatabg
astrodata.bg SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for astrodata.bg is good at 23 characters: "Хороскоп - AstroData.bg". The length is acceptable, though it may be slightly truncated in some search result displays.
The meta description is 60 characters (acceptable): "Дневен, седмичен, месечен и годишен хороскоп от AstroData.bg". 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://www.astrodata.bg/, preventing duplicate content issues.
Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Хороскоп..."), 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.
The meta keywords tag contains 11 terms including хороскоп, хороскопи, дневен хороскоп, седмичен хороскоп, and месечен хороскоп. 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
Хороскоп - AstroData.bg
https://astrodata.bg
Дневен, седмичен, месечен и годишен хороскоп от AstroData.bg
Meta Tags
TitleХороскоп - AstroData.bg...
Title Length23 chars
Meta Desc Length60 chars
H1—
Language—
Canonicalhttps://www.astrodata.bg/
Meta Robotsnot set
Meta Keywordsхороскоп, хороскопи, дневен хороскоп, седмичен хороскоп, мес...
Schema.org & Social
Schema Types—
OG Typewebsite
OG ImageSet ✓
Twitter Card—
FaviconNot set
Open Graph Preview
astrodata.bg
Хороскоп
Дневен, седмичен, месечен и годишен хороскоп от AstroData.bg
astrodata.bg 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 astrodata.bg. 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-84V249J3HR, meta_pixel_id: 300899700433414.
Tracking IDs for Cross-Referencing
ga4_idG-84V249J3HR
meta_pixel_id300899700433414
Related Domains
Related domain data requires database (populated after batch crawl)