11o0o.com

We performed a comprehensive analysis of 11o0o.com on 2026-06-27. The website returned an HTTP 200 status code with a server response time of 1134ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 85 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 40/100 (below average). The following security headers are properly configured: Content-Security-Policy and Strict-Transport-Security (HSTS). However, the site is missing 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 11o0o.com. The detected stack includes reCAPTCHA v3. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 11o0o.com receives an overall trust score of 62/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, 11o0o.com receives a trust score of 62/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 and HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks. Areas of concern include: 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 11o0o.com 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 11o0o.com 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. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for 11o0o.com.

11o0o.com resolves to the IPv4 address 13.248.243.5, 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 2 name servers: ns63.domaincontrol.com and ns64.domaincontrol.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. 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 11o0o.com. 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 25 active subdomains for 11o0o.com: admin.11o0o.com, api.11o0o.com, app.11o0o.com, apps.11o0o.com, blog.11o0o.com, cdn.11o0o.com, community.11o0o.com, and dev.11o0o.com. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The title tag for 11o0o.com is good at 9 characters: "11o0o.com". The length is acceptable, though it may be slightly truncated in some search result displays. No meta description is configured for 11o0o.com. 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 page language is declared as zh-sg and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("十一零零零..."), 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 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.