neo.space

We performed a comprehensive analysis of neo.space on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 18307ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 209 KB, and the site is served behind a CDN (Content Delivery Network). The website uses a secure HTTPS connection with a valid SSL certificate issued by Amazon (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2027-01-01, which is 185 days from now. The security headers analysis reveals a score of 55/100 (moderate). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), and X-Frame-Options. However, the site is missing 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 9 technologies across 7 categories powering neo.space. The detected stack includes Google Analytics 4, Hotjar, Amplitude, Google Tag Manager, Zendesk, Sentry, Amazon CloudFront, YouTube Embed, and jQuery 3.5.1.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, neo.space receives an overall trust score of 77/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, neo.space 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, a valid SSL certificate issued by Amazon with 185 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DMARC email authentication with a reject policy — the strongest available setting. Areas of concern include: 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 neo.space 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.

Our technology detection engine scanned neo.space and identified 9 distinct technologies across 7 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, Hotjar, and Amplitude — tracks visitor behavior and provides traffic insights for neo.space. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for neo.space. Support: Zendesk — handles customer support tickets and knowledge bases for neo.space. Monitoring: Sentry — monitors application performance and errors for neo.space. CDN: Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for neo.space. Video: YouTube Embed — provides video hosting and playback for neo.space. JavaScript Library: jQuery (version 3.5.1.) — provides utility functions and DOM manipulation for neo.space. We also extracted the following tracking identifiers: Google Tag Manager container GTM-NMVB3JR and Hotjar Site ID 2304920. These IDs can be used to identify other websites operated by the same organization.

neo.space delivers its homepage in 18307ms (server response time), which is considered slow by industry standards. The total page weight is 209 KB, and we detected 241 resource requests loading assets from 16 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: 2 out of 2 CSS files and 6 out of 8 JavaScript files are minified. Minifying the remaining 2 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 neo.space produces approximately 0.1g 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 209 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for neo.space. 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.

neo.space resolves to the IPv4 address 100.59.86.112, 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 4 A record(s) configured. The domain name system is managed by 4 name servers: ns-1433.awsdns-51.org, ns-1928.awsdns-49.co.uk, ns-213.awsdns-26.com, and ns-835.awsdns-40.net. Having 4 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 neo.space is handled by neo.space with 2 MX records configured: mx0001.neo.space and mx0002.neo.space. 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 not enabled for neo.space. 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 neo.space: admin.neo.space, api.neo.space, app.neo.space, and www.neo.space. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of neo.space contains 2,333 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 15 H2 headings, 2 H3 headings, 35 H4 headings, 5 H5, and 0 H6 headings. The page includes 104 images. 95 images (91%) 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 9% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 84 internal links pointing to other pages on the same domain and 12 external links pointing to third-party websites. There are 8 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), robots.txt (controls search engine crawling behavior), and Schema.org structured data (AggregateRating and Product). The website has social media presence across 3 platforms: Instagram (@tryneospace), Linkedin (@neo-email), and Youtube (@neo-space). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for neo.space is too long at 77 characters: "Business Email With Free Domain & Free AI Site | Neo Mail + Neo Sites: by Neo". At 77 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 186 characters (slightly long): "Neo is an all-in-one platform (Neo Mail, Neo Sites) where small businesses can create business email accounts with a fre...". 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.neo.space/, preventing duplicate content issues, the page language is declared as en-us, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Business Email With Free Domain & Free AI Site | Neo Mail + ..."), OG description, 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: AggregateRating and Product. 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.