ioc.exchange

We performed a comprehensive analysis of ioc.exchange on 2026-07-01. The website returned an HTTP 200 status code with a server response time of 3413ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 49 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_256_GCM_SHA384 cipher suite and sha256WithRSAEncryption signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-09-07, which is 68 days from now. The security headers analysis reveals a score of 85/100 (good). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, and Referrer-Policy. However, the site is missing 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 ioc.exchange. The detected stack includes React. The UI is built with React. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, ioc.exchange receives an overall trust score of 82/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, ioc.exchange receives a trust score of 82/100, which places it in the "Very 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, a valid SSL certificate issued by Let's Encrypt with 68 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, and a well-established domain registered for over 6.7 years, indicating long-term commitment and legitimacy. 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 ioc.exchange 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 Porkbun LLC based in DE, with a registration date of 2019-10-26 and expiration date of 2027-10-26.

Our technology detection engine scanned ioc.exchange 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. UI Library: React — handles the user interface rendering and component management for ioc.exchange.

ioc.exchange delivers its homepage in 3413ms (server response time), which is considered slow by industry standards. The total page weight is 49 KB, and we detected 172 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: 0 out of 17 CSS files and 0 out of 3 JavaScript files are minified. Minifying the remaining 20 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 ioc.exchange produces approximately 0.02g 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 49 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for ioc.exchange. 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.

ioc.exchange resolves to the IPv4 address 46.4.252.37 and also supports IPv6 (2a01:4f8:2b03:ba1::2), demonstrating modern network infrastructure readiness. The domain has 1 A record(s) configured. The domain name system is managed by 2 name servers: coco.bunny.net and kiki.bunny.net. 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 ioc.exchange is handled by llama.one with 1 MX records configured: dino.llama.one. 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 was not detected. Without DKIM, recipients cannot cryptographically verify that emails claiming to be from this domain are authentic. DNSSEC is not enabled for ioc.exchange. 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 Porkbun LLC (DE). It was first registered on 2019-10-26 and is set to expire on 2027-10-26, making it 6.7 years old.

The homepage of ioc.exchange 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 page includes 1 image. 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 0 internal links pointing to other pages on the same domain and 1 external link pointing to third-party websites. There are 3 external JavaScript files, 17 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: robots.txt (controls search engine crawling behavior) and Progressive Web App (PWA) manifest (enabling app-like installation). Notable missing features: XML Sitemap 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: Github (@glitch-soc). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for ioc.exchange is good at 12 characters: "IOC.exchange". The length is acceptable, though it may be slightly truncated in some search result displays. The meta description is 163 characters (slightly long): "INDICATORS OF COMPROMISE (IOC) InfoSec Community within the Fediverse. Newbies, experts, gurus - Everyone is Welcome! In...". 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 en and a favicon is configured. Open Graph meta tags are configured with 4/4 recommended fields: OG title ("IOC.exchange..."), 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.