orum.com

We performed a comprehensive analysis of orum.com on 2026-07-08. The website returned an HTTP 200 status code with a server response time of 12421ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 556 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_128_GCM_SHA256 cipher suite and ECDSA-SHA384 signature algorithm. The certificate covers 1 domain(s) (Subject Alternative Names) and expires on 2026-09-15, which is 69 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-Content-Type-Options, Referrer-Policy, and Permissions-Policy. However, the site is missing X-Frame-Options, which could expose the site and its users to cross-site scripting (XSS), clickjacking, and other web-based attacks. Our technology detection scan identified 7 technologies across 6 categories powering orum.com. The detected stack includes Next.js css, Webpack, Vite, Google Tag Manager, LinkedIn Insight Tag, VWO, and HubSpot. The site uses Next.js as its primary framework (version css). Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, orum.com receives an overall trust score of 82/100, classified as "Very Likely Safe".

After conducting a thorough safety and legitimacy analysis, orum.com 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 69 days until expiration, SPF (Sender Policy Framework) email authentication preventing email spoofing, DMARC email authentication with a quarantine policy, and DNSSEC providing authenticated DNS responses. Areas of concern include: no X-Frame-Options header, which could allow the site to be embedded in malicious iframes (clickjacking) 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 orum.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.

Our technology detection engine scanned orum.com and identified 7 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. Framework: Next.js (version css) — provides the application framework and routing for orum.com. Build Tool: Webpack and Vite — bundles and optimizes the JavaScript and CSS assets for orum.com. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for orum.com. Advertising: LinkedIn Insight Tag — handles advertising pixel tracking and conversion measurement for orum.com. A/B Testing: VWO — enables experimentation and conversion optimization for orum.com. Marketing: HubSpot — provides marketing automation capabilities for orum.com. We also extracted the following tracking identifiers: Google Tag Manager container GTM-K6ZPWHS. These IDs can be used to identify other websites operated by the same organization.

orum.com delivers its homepage in 12421ms (server response time), which is considered slow by industry standards. The total page weight is 556 KB, and we detected 173 resource requests loading assets from 11 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 2 CSS files and 0 out of 22 JavaScript files are minified. Minifying the remaining 24 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 orum.com produces approximately 0.27g of CO₂, earning a carbon rating of C. This is an average carbon footprint. Optimizing images and reducing unnecessary scripts could further improve this score. For reference, the average web page produces about 0.5g of CO₂ per page view. The page weight of 556 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for orum.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.

orum.com resolves to the IPv4 address 104.198.168.220, 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: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, and ns-cloud-e4.googledomains.com. 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 orum.com is handled by Google Workspace with 5 MX records configured: aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com and 2 more. 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 enabled for orum.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 homepage of orum.com contains 1,255 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 11 H2 headings, 12 H3 headings, 0 H4 headings. The page includes 41 images. 28 images (68%) 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 32% of images have proper alt text — we recommend adding descriptive alt attributes to all images. The link structure consists of 68 internal links pointing to other pages on the same domain and 19 external links pointing to third-party websites. There are 22 external JavaScript files, 2 CSS stylesheets, and 1 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 (@orumhq), Linkedin (@orumhq), and Youtube (@Orum). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for orum.com is well-optimized at 53 characters: "Orum - The Calling Performance System for Sales Teams". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 118 characters (well-optimized): "Orum is the AI-powered Live Conversation Platform to supercharge sales activity, connect teams, and drive more revenue". 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.orum.com/, preventing duplicate content issues, the page language is declared as en, 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 ("The Calling Performance System for Sales Teams..."), 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.