kmdfd.org

We performed a comprehensive analysis of kmdfd.org on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 11945ms. The page is served over HTTP/1.1 protocol, however no compression (Gzip or Brotli) is enabled, which means the page is transferred at its full uncompressed size. The total page weight is 15 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 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 2 technologies across 2 categories powering kmdfd.org. The detected stack includes jQuery 1.8.3. and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, kmdfd.org receives an overall trust score of 45/100, classified as "Caution Advised".

After conducting a thorough safety and legitimacy analysis, kmdfd.org receives a trust score of 45/100, which places it in the "Caution Advised" 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. 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 kmdfd.org 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 kmdfd.org and identified 2 distinct technologies across 2 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. JavaScript Library: jQuery (version 1.8.3.) — provides utility functions and DOM manipulation for kmdfd.org. Icon Set: Font Awesome — provides additional functionality for kmdfd.org.

kmdfd.org delivers its homepage in 11945ms (server response time), which is considered slow by industry standards. The total page weight is 15 KB, and we detected 72 resource requests loading assets from 8 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. No compression is currently enabled on kmdfd.org. Enabling Brotli or Gzip compression could reduce page size by 60-80% for text-based assets (HTML, CSS, JavaScript), significantly improving load times and reducing bandwidth costs. This is one of the simplest and most impactful performance optimizations available. Asset minification status: 1 out of 8 CSS files and 5 out of 10 JavaScript files are minified. Minifying the remaining 12 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 kmdfd.org produces approximately 0.01g 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 15 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for kmdfd.org. 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.

kmdfd.org resolves to the IPv4 address 175.126.82.156, 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 4 name servers: ns1.cafe24.co.kr, ns1.cafe24.com, ns2.cafe24.co.kr, and ns2.cafe24.com. 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 kmdfd.org. 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 kmdfd.org contains 88 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 1 H2 headings, 3 H3 headings, 1 H4 headings. The page includes 7 images. All images have proper alt text attributes ✓, which is excellent for both accessibility (screen readers) and SEO (search engines can understand image content). The link structure consists of 33 internal links pointing to other pages on the same domain and 6 external links pointing to third-party websites. There are 10 external JavaScript files, 8 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 kmdfd.org is good at 10 characters: "재단법인 김만덕재단". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 57 characters (acceptable): "재단법인 김만덕재단, 김만덕, 나눔, 봉사, 제주, 노블리스오블리제, 은광연세, 김만덕기념관, 나눔교육". 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 page language is declared as ko. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("재단법인 김만덕재단..."), 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. The meta keywords tag contains 8 terms including 김만덕, 나눔, 봉사, 제주, and 노블리스오블리제. 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.