lyrebirdstudio.net

We performed a comprehensive analysis of lyrebirdstudio.net on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 7226ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 638 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-02-11, which is 226 days from now. 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 3 technologies across 3 categories powering lyrebirdstudio.net. The detected stack includes Next.js css, React, and Webpack. The site uses Next.js as its primary framework (version css). The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, lyrebirdstudio.net receives an overall trust score of 66/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, lyrebirdstudio.net receives a trust score of 66/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, a valid SSL certificate issued by Amazon with 226 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, and a well-established domain registered for over 12.7 years, indicating long-term commitment and legitimacy. 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 lyrebirdstudio.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. The domain is registered through PDR Ltd. d/b/a PublicDomainRegistry.com based in IE, with a registration date of 2013-11-07 and expiration date of 2028-11-07.

Our technology detection engine scanned lyrebirdstudio.net and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Framework: Next.js (version css) — provides the application framework and routing for lyrebirdstudio.net. UI Library: React — handles the user interface rendering and component management for lyrebirdstudio.net. Build Tool: Webpack — bundles and optimizes the JavaScript and CSS assets for lyrebirdstudio.net.

lyrebirdstudio.net delivers its homepage in 7226ms (server response time), which is considered slow by industry standards. The total page weight is 638 KB, and we detected 64 resource requests loading assets from 4 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 2 CSS files and 0 out of 5 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. 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 lyrebirdstudio.net produces approximately 0.31g 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 638 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for lyrebirdstudio.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.

lyrebirdstudio.net resolves to the IPv4 address 108.156.22.67, 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-1121.awsdns-12.org, ns-1647.awsdns-13.co.uk, ns-366.awsdns-45.com, and ns-715.awsdns-25.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 lyrebirdstudio.net is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 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 was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for lyrebirdstudio.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. The domain is registered through PDR Ltd. d/b/a PublicDomainRegistry.com (IE). It was first registered on 2013-11-07 and is set to expire on 2028-11-07, making it 12.7 years old. Our subdomain enumeration scan discovered 2 active subdomains for lyrebirdstudio.net: cdn.lyrebirdstudio.net and www.lyrebirdstudio.net. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of lyrebirdstudio.net contains 670 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 28 images. 25 images (89%) 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 11% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 5 internal links pointing to other pages on the same domain and 7 external links pointing to third-party websites. There are 5 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, Brand, ContactPoint, Offer, Organization, Person, and SoftwareApplication). We detected the following payment methods accepted on lyrebirdstudio.net: JCB. 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 4 platforms: Facebook (@lyrebirdstudio), Twitter (@lyrebirdstudio), Instagram (@lyrebirdstudio), and Linkedin (@lyrebird-studio). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for lyrebirdstudio.net is well-optimized at 45 characters: "LyrebirdStudio - AI Photo & Face Editing Apps". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 181 characters (slightly long): "Create stunning photos with LyrebirdStudio's AI-powered apps. Transform selfies into cartoons with ToonApp, enhance beau...". 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://lyrebirdstudio.net, preventing duplicate content issues, the page language is declared as en, and the meta robots directive is set to index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("LyrebirdStudio - AI Photo & Face Editing Apps..."), 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: AggregateRating, Brand, ContactPoint, Offer, Organization, Person, and SoftwareApplication. 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 15 terms including LyrebirdStudio, FaceLab, Cosmo, ToonApp, and AI Photo Editor. 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.