beaconhouse.net Website Overview & Technology Report
🤖 AI Summary
We performed a comprehensive analysis of beaconhouse.net on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 18515ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 76 KB, and the site is served behind a CDN (Content Delivery Network).
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 15/100 (poor). The following security headers are properly configured: X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-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 9 technologies across 9 categories powering beaconhouse.net. The detected stack includes WordPress 6.9.4, Bootstrap, Google Analytics 4, Meta Pixel, Tawk.to, StackPath, Google Fonts, jQuery, and Font Awesome.
Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, beaconhouse.net receives an overall trust score of 61/100, classified as "Likely Safe".
HTTP Response
Status200 OK
Response Time18515ms
ProtocolHTTP/2
Page Size76 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Servercloudflare
Total Requests193
3rd Party Domains26
Redirect1 hop(s)
Detected Technologies (9)
• WordPress
🎨 Bootstrap
📊 Google Analytics 4
📢 Meta Pixel
💬 Tawk.to
☁️ StackPath
🔤 Google Fonts
📦 jQuery
🎯 Font Awesome
Security Headers
✗
Content-Security-Policy
Not set
✗
Strict-Transport-Security (HSTS)
Not set
✗
X-Frame-Options
Not set
✓
X-Content-Type-Options
Set ✓
✗
Referrer-Policy
Not set
✗
Permissions-Policy
Not set
SSL Certificate
IssuerGoogle Trust Services
Issuer FullcountryName=US, organizationName=Google Trust Services, commonName=WE1
SubjectcommonName=beaconhouse.net
Type—
TLS VersionTLS 1.3
Cipher SuiteTLS_AES_256_GCM_SHA384
Algorithm—
Issued—
Expires— (? days)
SANs—
beaconhouse.net Trust Score & Safety Analysis
🤖 AI Summary
After conducting a thorough safety and legitimacy analysis, beaconhouse.net 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 quarantine 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 beaconhouse.net 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=quarantine)
✅ 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
beaconhouse.net Technology Stack & Detected Technologies
🤖 AI Summary
Our technology detection engine scanned beaconhouse.net and identified 9 distinct technologies across 9 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records.
CMS: WordPress (version 6.9.4) — manages the content and page structure for beaconhouse.net.
CSS Framework: Bootstrap — provides the styling and responsive layout system for beaconhouse.net.
Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for beaconhouse.net.
Advertising: Meta Pixel — handles advertising pixel tracking and conversion measurement for beaconhouse.net.
Chat: Tawk.to — provides live chat and customer communication for beaconhouse.net.
CDN: StackPath — accelerates content delivery by caching assets at edge locations worldwide for beaconhouse.net.
Fonts: Google Fonts — delivers web fonts for typography for beaconhouse.net.
JavaScript Library: jQuery — provides utility functions and DOM manipulation for beaconhouse.net.
Icon Set: Font Awesome — provides additional functionality for beaconhouse.net.
We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-DBF9LFZRD8 and Meta (Facebook) Pixel ID 785298768962489. These IDs can be used to identify other websites operated by the same organization.
CMS
CSS Framework
Analytics
📊 Google Analytics 4(95%)
Advertising
Chat
CDN
Fonts
JavaScript Library
Icon Set
Tracking IDs
ga4_idG-DBF9LFZRD8
meta_pixel_id785298768962489
beaconhouse.net Performance, Speed & Core Web Vitals
🤖 AI Summary
beaconhouse.net delivers its homepage in 18515ms (server response time), which is considered slow by industry standards. The total page weight is 76 KB, and we detected 193 resource requests loading assets from 26 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: 10 out of 31 CSS files and 9 out of 25 JavaScript files are minified. Minifying the remaining 37 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.
The site is served through a Content Delivery Network (CDN), which caches static assets at edge servers around the world. This means visitors from different geographic regions receive content from the nearest edge server, significantly reducing latency. CDN usage is particularly important for websites with a global audience, as it can reduce page load times by 40-60% for distant visitors.
From an environmental perspective, each page view of beaconhouse.net 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 76 KB is the primary factor in this calculation.
Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for beaconhouse.net. 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 Size76 KB
CompressionGzip
Compression Savings~60.0%
CDNYes ✓
Total Requests193
3rd Party Domains26
CSS Minified10/31
JS Minified9/25
beaconhouse.net DNS Records, Email Authentication & Domain Registration
🤖 AI Summary
beaconhouse.net resolves to the IPv4 address 162.159.134.42 and also supports IPv6 (2606:4700:7::a29f:862a), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured.
The domain name system is managed by 2 name servers: cruz.ns.cloudflare.com and nile.ns.cloudflare.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 beaconhouse.net is handled by Google Workspace with 7 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 4 more. 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 quarantine policy — a moderate setting, directing unauthorized emails to spam/junk folders. 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 beaconhouse.net. 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 3 active subdomains for beaconhouse.net: app.beaconhouse.net, cdn.beaconhouse.net, and www.beaconhouse.net. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.
DNS Records
A
162.159.134.42
162.159.135.42
NS
cruz.ns.cloudflare.com
nile.ns.cloudflare.com
MX
aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
aspmx2.googlemail.com
aspmx3.googlemail.com
aspmx4.googlemail.com
aspmx5.googlemail.com
Email & Authentication
MX ProviderGoogle Workspace
Registrar—
Organisation—
Country—
Contact—
Registered—
Expires—
Domain Age—
IPv6 SupportYes ✓
Subdomains (3 found)
app.beaconhouse.net cdn.beaconhouse.net www.beaconhouse.net
beaconhouse.net Page Content, Images & Accessibility
🤖 AI Summary
The homepage of beaconhouse.net contains 306 words of visible text content. This is a moderate amount of content. The page is structured with 7 H2 headings, 2 H3 headings, 0 H4 headings.
The page includes 64 images. 64 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 32 internal links pointing to other pages on the same domain and 33 external links pointing to third-party websites. There are 25 external JavaScript files, 31 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), Schema.org structured data (BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite), and RSS feed for content syndication.
Notable missing features: robots.txt. Adding these could improve search engine discoverability and rich result eligibility.
We detected the following payment methods accepted on beaconhouse.net: Discover. Offering multiple payment options including credit cards and digital wallets improves customer trust and can increase conversion rates.
The website has social media presence across 3 platforms: Facebook (@BeaconhouseSchoolSystemOfficial), Twitter (@BSSWorldwide), and Instagram (@bssworldwide). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.
Content Structure
H1—
H2 Tags7
H3 Tags2
H4 Tags0
H5 Tags0
H6 Tags0
Internal Links32
External Links33
Assets & Features
JavaScript Files25
JS Minified9/25
CSS Files31
CSS Minified10/31
Iframes0
Images64
Missing Alt64
SitemapYes ✓
Robots.txtNo
PWANo
AMPNo
RSS FeedYes ✓
Schema.org Types
BreadcrumbListEntryPointImageObjectListItemOrganizationPropertyValueSpecificationReadActionSearchActionWebPageWebSite
Payment Methods Detected
Social Media Presence
Facebook: @BeaconhouseSchoolSystemOfficialTwitter: @BSSWorldwideInstagram: @bssworldwide
beaconhouse.net SEO Analysis, Meta Tags & Open Graph
🤖 AI Summary
The title tag for beaconhouse.net is good at 18 characters: "Home - Beaconhouse". The length is acceptable, though it may be slightly truncated in some search result displays.
No meta description is configured for beaconhouse.net. 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 canonical url is correctly set to https://www.beaconhouse.net/, preventing duplicate content issues, the page language is declared as en-us, the meta robots directive is set to index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1, and a favicon is configured.
Open Graph meta tags are configured with 2/4 recommended fields: OG title ("Home - Beaconhouse..."), 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.
A Twitter Card of type summary_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type.
The site implements Schema.org structured data with the following types: BreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, and WebSite. Structured data helps search engines understand the page content and can enable rich results (featured snippets, knowledge panels, star ratings) in Google search results, which can significantly increase click-through rates.
Google SERP Preview
Home - Beaconhouse
https://beaconhouse.net
Meta Tags
TitleHome - Beaconhouse...
Title Length18 chars
Meta Desc Length0 chars
H1—
Languageen-US
Canonicalhttps://www.beaconhouse.net/
Meta Robotsindex, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Meta Keywordsnot set
Schema.org & Social
Schema TypesBreadcrumbList, EntryPoint, ImageObject, ListItem, Organization, PropertyValueSpecification, ReadAction, SearchAction, WebPage, WebSite
OG Typewebsite
OG ImageNot set
Twitter Cardsummary_large_image
FaviconSet ✓
beaconhouse.net 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 beaconhouse.net. 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-DBF9LFZRD8, meta_pixel_id: 785298768962489.
Tracking IDs for Cross-Referencing
ga4_idG-DBF9LFZRD8
meta_pixel_id785298768962489
Related Domains
Related domain data requires database (populated after batch crawl)