riskiq.com

We performed a comprehensive analysis of riskiq.com on 2026-07-02. The website returned an HTTP 200 status code with a server response time of 3189ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 213 KB. The website uses a secure HTTPS connection with a valid SSL certificate issued by Microsoft Corporation (DV type). The connection is encrypted using TLS 1.3 with the TLS_AES_128_GCM_SHA256 cipher suite. The certificate covers 202 domain(s) (Subject Alternative Names) and expires on 2026-10-12, which is 102 days from now. The security headers analysis reveals a score of 20/100 (poor). The following security headers are properly configured: Strict-Transport-Security (HSTS). However, the site is missing Content-Security-Policy, 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 3 technologies across 3 categories powering riskiq.com. The detected stack includes Vite, Microsoft Clarity, and jQuery. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, riskiq.com receives an overall trust score of 74/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, riskiq.com receives a trust score of 74/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, a valid SSL certificate issued by Microsoft Corporation with 102 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a reject policy — the strongest available setting, DNSSEC providing authenticated DNS responses, and a well-established domain registered for over 20.5 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, 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 riskiq.com 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 Nom-iq Ltd. dba COM LAUDE based in AU, with a registration date of 2006-01-12 and expiration date of 2027-01-12.

Our technology detection engine scanned riskiq.com and identified 3 distinct technologies across 3 categories. This analysis is performed by examining HTTP response headers, HTML source code patterns, JavaScript library fingerprints, CSS framework signatures, and DNS records. Build Tool: Vite — bundles and optimizes the JavaScript and CSS assets for riskiq.com. Analytics: Microsoft Clarity — tracks visitor behavior and provides traffic insights for riskiq.com. JavaScript Library: jQuery — provides utility functions and DOM manipulation for riskiq.com.

riskiq.com delivers its homepage in 3189ms (server response time), which is considered slow by industry standards. The total page weight is 213 KB, and we detected 284 resource requests loading assets from 27 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: 24 out of 26 CSS files and 49 out of 56 JavaScript files are minified. Minifying the remaining 9 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 riskiq.com produces approximately 0.1g 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 213 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for riskiq.com. 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.

riskiq.com resolves to the IPv4 address 20.70.246.20, 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 5 A record(s) configured. The domain name system is managed by 4 name servers: ns1-86.azure-dns.com, ns2-86.azure-dns.net, ns3-86.azure-dns.org, and ns4-86.azure-dns.info. 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 riskiq.com is handled by Microsoft 365 with 2 MX records configured: riskiq-com.v-v1.mx.microsoft and microsoft-com.mail.protection.outlook.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 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 enabled for riskiq.com, 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. The domain is registered through Nom-iq Ltd. dba COM LAUDE (AU). It was first registered on 2006-01-12 and is set to expire on 2027-01-12, making it 20.5 years old. Our subdomain enumeration scan discovered 9 active subdomains for riskiq.com: admin.riskiq.com, api.riskiq.com, app.riskiq.com, blog.riskiq.com, dev.riskiq.com, m.riskiq.com, mail.riskiq.com, and shop.riskiq.com. Plus 1 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The homepage of riskiq.com contains 1,149 words of visible text content. This is a substantial amount of content that provides good opportunities for search engine indexing. The page is structured with 12 H2 headings, 22 H3 headings, 2 H4 headings. The page includes 23 images. 5 images (22%) 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 78% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 116 internal links pointing to other pages on the same domain and 55 external links pointing to third-party websites. The high number of internal links suggests a well-interconnected site structure, which helps search engines discover and crawl all pages efficiently. There are 56 external JavaScript files, 26 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 riskiq.com is well-optimized at 59 characters: "Microsoft Defender Threat Intelligence | Microsoft Security". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 153 characters (well-optimized): "Suojaa organisaatiosi nykyaikaisilta kyberuhkilta ja altistumiselta Microsoft Defender Threat Intelligencen avulla, joka...". 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 canonical url is correctly set to https://www.microsoft.com/fi-fi/security/business/siem-and-xdr/microsoft-defender-threat-intelligence, preventing duplicate content issues, the page language is declared as fi-fi, the meta robots directive is set to index, follow, and a favicon is configured. Open Graph meta tags are configured with 3/4 recommended fields: OG title ("Microsoft Defender Threat Intelligence | Microsoft Security..."), 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. 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.