kgrr.org

We performed a comprehensive analysis of kgrr.org on 2026-06-30. The website returned an HTTP 200 status code with a server response time of 10276ms. The page is served over HTTP/2 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 25 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 30/100 (below average). The following security headers are properly configured: X-Frame-Options and X-Content-Type-Options. However, the site is missing Content-Security-Policy, Strict-Transport-Security (HSTS), 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 6 technologies across 6 categories powering kgrr.org. The detected stack includes Google Analytics 4, Google Tag Manager, Cloudflare, Google Fonts, jQuery 3.5.1., and Font Awesome. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, kgrr.org receives an overall trust score of 64/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, kgrr.org receives a trust score of 64/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, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, and a well-established domain registered for over 21.8 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, 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 kgrr.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. The domain is registered through GMO Internet Group, Inc. d/b/a Onamae.com based in JP, with a registration date of 2004-09-20 and expiration date of 2033-09-20.

Our technology detection engine scanned kgrr.org and identified 6 distinct technologies across 6 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for kgrr.org. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for kgrr.org. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for kgrr.org. Fonts: Google Fonts — delivers web fonts for typography for kgrr.org. JavaScript Library: jQuery (version 3.5.1.) — provides utility functions and DOM manipulation for kgrr.org. Icon Set: Font Awesome — provides additional functionality for kgrr.org. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-4LNR8M4MQ5 and Google Tag Manager container GTM-NPPDKST. These IDs can be used to identify other websites operated by the same organization.

kgrr.org delivers its homepage in 10276ms (server response time), which is considered slow by industry standards. The total page weight is 25 KB, and we detected 110 resource requests loading assets from 16 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 kgrr.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: 3 out of 6 CSS files and 2 out of 5 JavaScript files are minified. Minifying the remaining 6 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 kgrr.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 25 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for kgrr.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.

kgrr.org resolves to the IPv4 address 150.95.34.182, 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: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, and 04.dnsv.jp. 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 kgrr.org is handled by amazonaws.com with 1 MX records configured: inbound-smtp.us-west-2.amazonaws.com. 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 kgrr.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 domain is registered through GMO Internet Group, Inc. d/b/a Onamae.com (JP). It was first registered on 2004-09-20 and is set to expire on 2033-09-20, making it 21.8 years old. Our subdomain enumeration scan discovered 2 active subdomains for kgrr.org: admin.kgrr.org and www.kgrr.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of kgrr.org contains 147 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 page includes 18 images. 12 images (67%) 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 33% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 49 internal links pointing to other pages on the same domain and 14 external links pointing to third-party websites. There are 5 external JavaScript files, 6 CSS stylesheets, and 2 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 website has social media presence across 3 platforms: Twitter (@kgrr_official), Instagram (@kgrr_official), and Youtube (@UCfgvCFaOz7iWS4nSWEhyDCQ). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for kgrr.org is good at 17 characters: "一般社団法人 関東学生陸上競技連盟". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 29 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 ja and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("一般社団法人 関東学生陸上競技連盟..."), 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.