examiner.org

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, examiner.org receives a trust score of 58/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. The analysis identified several positive trust signals: a valid HTTPS connection protecting data in transit, SPF (Sender Policy Framework) email authentication preventing email spoofing, and DNSSEC providing authenticated DNS responses. 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, and the domain's WHOIS information is hidden behind a privacy service, making it harder to verify the owner's identity. While these issues don't necessarily indicate malicious intent, they represent areas where the website's security posture could be improved. We checked examiner.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.

🤖 AI Summary

Our technology detection engine scanned examiner.org and identified 7 distinct technologies across 7 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. CMS: WordPress (version 6.9.4) — manages the content and page structure for examiner.org. Ecommerce: WooCommerce — powers the online store and shopping functionality for examiner.org. Analytics: Google Analytics 4 — tracks visitor behavior and provides traffic insights for examiner.org. Advertising: Google AdSense — handles advertising pixel tracking and conversion measurement for examiner.org. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for examiner.org. Fonts: Google Fonts — delivers web fonts for typography for examiner.org. JavaScript Library: jQuery — provides utility functions and DOM manipulation for examiner.org. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-XFFHR8YFVX. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

examiner.org delivers its homepage in 1315ms (server response time), which is considered somewhat slow by industry standards. The total page weight is 139 KB, and we detected 178 resource requests loading assets from 19 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: 2 out of 23 CSS files and 19 out of 37 JavaScript files are minified. Minifying the remaining 39 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 examiner.org produces approximately 0.07g 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 139 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for examiner.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.

🤖 AI Summary

examiner.org resolves to the IPv4 address 172.67.182.36 and also supports IPv6 (2606:4700:3031::6815:200f), demonstrating modern network infrastructure readiness. The domain has 2 A record(s) configured. The domain name system is managed by 2 name servers: marge.ns.cloudflare.com and titan.ns.cloudflare.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 examiner.org is handled by ppe-hosted.com with 2 MX records configured: mx1-us1.ppe-hosted.com and mx2-us1.ppe-hosted.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 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 enabled for examiner.org, providing an additional layer of security by cryptographically signing DNS records. This prevents DNS cache poisoning and man-in-the-middle attacks that could redirect visitors to malicious websites. Our subdomain enumeration scan discovered 25 active subdomains for examiner.org: admin.examiner.org, api.examiner.org, app.examiner.org, apps.examiner.org, blog.examiner.org, cdn.examiner.org, community.examiner.org, and dev.examiner.org. Plus 17 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of examiner.org contains 303 words of visible text content. This is a moderate amount of content. The page is structured with 0 H2 headings, 10 H3 headings, 0 H4 headings. The page includes 21 images. 21 images (100%) 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 0% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 59 internal links pointing to other pages on the same domain and 9 external links pointing to third-party websites. There are 37 external JavaScript files, 23 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: RSS feed for content syndication. 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 1 platforms: Facebook (@bellefontaineexaminer). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for examiner.org is well-optimized at 56 characters: "Bellefontaine Examiner | Serving Logan County Since 1891". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. No meta description is configured for examiner.org. 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 canonical url is correctly set to https://examiner.org/, preventing duplicate content issues, the page language is declared as en-us, the meta robots directive is set to noindex, nofollow, and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("Bellefontaine Examiner..."), 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 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.

🤖 AI Summary

Related domain discovery works by finding other websites that share the same IP address, Google Tag Manager container ID, Google Analytics property, or advertising pixel IDs with examiner.org. This data becomes available after batch-crawling the domain database — individual domain lookups cannot populate this section. We extracted the following tracking IDs that can be used for cross-referencing: ga4_id: G-XFFHR8YFVX.