dnslog.ink

We performed a comprehensive analysis of dnslog.ink on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 11599ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 3 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 1 domain(s) (Subject Alternative Names) and expires on 2026-08-13, which is 44 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 1 technologies across 1 categories powering dnslog.ink. The detected stack includes Bootstrap. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, dnslog.ink receives an overall trust score of 63/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, dnslog.ink receives a trust score of 63/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 Let's Encrypt with 44 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, and a domain registered for 1.6 years. 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 dnslog.ink 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 NameCheap, Inc. based in SG, with a registration date of 2024-11-20 and expiration date of 2026-11-20.

Our technology detection engine scanned dnslog.ink 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. CSS Framework: Bootstrap — provides the styling and responsive layout system for dnslog.ink.

dnslog.ink delivers its homepage in 11599ms (server response time), which is considered slow by industry standards. The total page weight is 3 KB, and we detected 9 resource requests loading assets from 1 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: 1 out of 2 CSS files and 0 out of 1 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. From an environmental perspective, each page view of dnslog.ink produces approximately 0.0g 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 3 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for dnslog.ink. 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.

dnslog.ink resolves to the IPv4 address 134.209.107.209, 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 1 A record(s) configured. The domain name system is managed by 2 name servers: dns1.registrar-servers.com and dns2.registrar-servers.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 dnslog.ink is handled by registrar-servers.com with 5 MX records configured: eforward1.registrar-servers.com, eforward2.registrar-servers.com, and eforward3.registrar-servers.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 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 dnslog.ink. 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 NameCheap, Inc. (SG). It was first registered on 2024-11-20 and is set to expire on 2026-11-20, making it 1.6 years old. Our subdomain enumeration scan discovered 1 active subdomains for dnslog.ink: admin.dnslog.ink. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of dnslog.ink contains 22 words of visible text content. This is a relatively short page — adding more descriptive content could improve search engine visibility. The page is structured with 0 H2 headings, 0 H3 headings, 0 H4 headings. The link structure consists of 4 internal links pointing to other pages on the same domain and 0 external links pointing to third-party websites. There are 1 external JavaScript files, 2 CSS stylesheets, and 0 iframes on the page. Notable missing features: XML Sitemap, robots.txt, and Schema.org structured data. Adding these could improve search engine discoverability and rich result eligibility.

The title tag for dnslog.ink is good at 25 characters: "DNSLog Platform -- DNSLog". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 63 characters (acceptable): "A DNSLog platform that can be used quickly without registration". 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://getbootstrap.com/docs/5.1/examples/dashboard/, preventing duplicate content issues, the page language is declared as zh-cn, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to dnslog.ink on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing. The meta keywords tag contains 4 terms including dnslog, dnslog platform, httplog, and weblog. 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.