namsor.app

We performed a comprehensive analysis of namsor.app on 2026-07-03. The website returned an HTTP 200 status code with a server response time of 9223ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 718 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Let's Encrypt (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite and ECDSA-SHA384 signature algorithm. The certificate covers 2 domain(s) (Subject Alternative Names) and expires on 2026-08-12, which is 40 days from now. The security headers analysis reveals a score of 65/100 (moderate). The following security headers are properly configured: Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing Content-Security-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 6 technologies across 5 categories powering namsor.app. The detected stack includes Gatsby, Webpack, Google Analytics 4, Hotjar 2676218, reCAPTCHA v3, and Google Fonts. The site uses Gatsby as its primary framework. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, namsor.app receives an overall trust score of 74/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, namsor.app receives a trust score of 74/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, and a valid SSL certificate issued by Let's Encrypt with 40 days until expiration. Areas of concern include: the absence of a Content-Security-Policy header, which leaves the site more vulnerable to cross-site scripting (XSS) attacks, 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 namsor.app 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 namsor.app and identified 6 distinct technologies across 5 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Gatsby — provides the application framework and routing for namsor.app. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for namsor.app. Analytics: Google Analytics 4 and Hotjar (version 2676218) — tracks visitor behavior and provides traffic insights for namsor.app. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for namsor.app. Fonts: Google Fonts — delivers web fonts for typography for namsor.app. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-TFVHRFZRFM and Hotjar Site ID 2676218. These IDs can be used to identify other websites operated by the same organization.

namsor.app delivers its homepage in 9223ms (server response time), which is considered slow by industry standards. The total page weight is 718 KB, and we detected 242 resource requests loading assets from 11 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 7 JavaScript files are minified. Minifying the remaining 7 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 namsor.app produces approximately 0.35g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 718 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for namsor.app. 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.

namsor.app resolves to the IPv4 address 35.157.26.135, 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 2 A record(s) configured. The domain name system is managed by 4 name servers: dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, and dns4.p02.nsone.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. 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 namsor.app. 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.

The homepage of namsor.app contains 2,986 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 7 H2 headings, 26 H3 headings, 13 H4 headings, 11 H5, and 12 H6 headings. The page includes 131 images. 39 images (30%) 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 70% 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 9 external links pointing to third-party websites. There are 7 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 Schema.org structured data (Organization). We detected the following payment methods accepted on namsor.app: Visa, Mastercard, and 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: Twitter (@namsor_com), Linkedin (@namsor), and Github (@namsor). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for namsor.app is good at 69 characters: "Namsor | Name analysis - Instant gender, origin & ethnicity detection". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 212 characters (slightly long): "Namsor revolutionizes name analysis with scientifically validated AI technology. Instantly discover gender, country of o...". 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://namsor.app/, preventing duplicate content issues, the page language is declared as en, the meta robots directive is set to index, follow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Namsor | Name analysis - Instant gender, origin & ethnicity ..."), 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. 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: Organization. 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. The meta keywords tag contains 22 terms including Namsor, namsor, name checker, gender of a name, and origin of a name. 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.