iskoop.org

🤖 AI Summary

After conducting a thorough safety and legitimacy analysis, iskoop.org receives a trust score of 77/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, HSTS (HTTP Strict Transport Security) enforcement preventing protocol downgrade attacks, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and DKIM (DomainKeys Identified Mail) providing cryptographic email verification. Areas of concern include: 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 iskoop.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 iskoop.org and identified 5 distinct technologies across 5 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 iskoop.org. Security: reCAPTCHA v3 — provides security features like bot detection and CAPTCHA for iskoop.org. CDN: Cloudflare — accelerates content delivery by caching assets at edge locations worldwide for iskoop.org. Fonts: Google Fonts — delivers web fonts for typography for iskoop.org. JavaScript Library: jQuery (version 3.6.0.) — provides utility functions and DOM manipulation for iskoop.org. We also extracted the following tracking identifiers: Google Analytics 4 Measurement ID G-N1YB7YYT0G. These IDs can be used to identify other websites operated by the same organization.

🤖 AI Summary

iskoop.org delivers its homepage in 8160ms (server response time), which is considered slow by industry standards. The total page weight is 70 KB, and we detected 175 resource requests loading assets from 14 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: 4 out of 8 CSS files and 11 out of 17 JavaScript files are minified. Minifying the remaining 10 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 iskoop.org produces approximately 0.03g 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 70 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for iskoop.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

iskoop.org resolves to the IPv4 address 213.194.102.104, 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 2 A record(s) configured. The domain name system is managed by 2 name servers: gina.ns.cloudflare.com and jaziel.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 iskoop.org is handled by iskoop.org with 1 MX records configured: mail.iskoop.org. 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 reject policy — the strongest setting, instructing receiving servers to reject unauthorized emails entirely. DKIM (DomainKeys Identified Mail) is configured, adding a cryptographic signature to outgoing emails that receiving servers can verify to confirm the email hasn't been tampered with in transit. DNSSEC is not enabled for iskoop.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. Our subdomain enumeration scan discovered 5 active subdomains for iskoop.org: api.iskoop.org, cdn.iskoop.org, mail.iskoop.org, portal.iskoop.org, and www.iskoop.org. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

🤖 AI Summary

The homepage of iskoop.org contains 427 words of visible text content. This is a moderate amount of content. The page is structured with 4 H2 headings, 23 H3 headings, 0 H4 headings. The page includes 14 images. 12 images (86%) 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 14% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 76 internal links pointing to other pages on the same domain and 39 external links pointing to third-party websites. There are 17 external JavaScript files, 8 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). Notable missing features: 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 5 platforms: Facebook (@istanbuleczakoop), Twitter (@ist_eczakoop), Instagram (@istanbuleczakoop), Linkedin (@isteczakoop), and Youtube (@UCpgzJHZmVIlrIHXhB2_78Bg). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

🤖 AI Summary

The title tag for iskoop.org is good at 18 characters: "İstanbul Ecza Koop". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 159 characters (acceptable): "İstanbul Eczacılar Kooperatifi 4000'i aşan ortağı, 1000'e yakın personeli, 22 ilde 19 şube ve 27 yıllık geçmişiyle eczac...". 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 tr and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("İstanbul Ecza Koop..."), OG description, OG image (social sharing thumbnail), 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 96 terms including Ecza Koop, İstanbul Koop, İskoop, Ecza deposu, and İstanbul ecza. 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.

🤖 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 iskoop.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-N1YB7YYT0G.