4me.qa

We performed a comprehensive analysis of 4me.qa on 2026-06-28. The website returned an HTTP 200 status code with a server response time of 22944ms. The page is served over HTTP/2 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 187 KB, and the site is served behind a CDN (Content Delivery Network). Warning: The website does not have a valid SSL certificate. Visitors may see security warnings in their browser, and data transmitted to and from this website is not encrypted. The security headers analysis reveals a score of 55/100 (moderate). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), and X-Frame-Options. However, the site is missing 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 5 technologies across 3 categories powering 4me.qa. The detected stack includes Google Tag Manager, Cloudflare, Fastly, Amazon CloudFront, and jQuery 3.5.1.. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, 4me.qa receives an overall trust score of 72/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, 4me.qa receives a trust score of 72/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: missing Referrer-Policy, potentially leaking URL information to third parties, 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 4me.qa 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 4me.qa and identified 5 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. Tag Manager: Google Tag Manager — manages marketing and analytics tags without code changes for 4me.qa. CDN: Cloudflare, Fastly, and Amazon CloudFront — accelerates content delivery by caching assets at edge locations worldwide for 4me.qa. JavaScript Library: jQuery (version 3.5.1.) — provides utility functions and DOM manipulation for 4me.qa. We also extracted the following tracking identifiers: Google Tag Manager container GTM-TNSN5JDV. These IDs can be used to identify other websites operated by the same organization.

4me.qa resolves to the IPv4 address 108.132.173.136 and also supports IPv6 (2a05:d018:863:3f01:258b:3bf6:f6c3:4d05), demonstrating modern network infrastructure readiness. The domain has 3 A record(s) configured. The domain name system is managed by 4 name servers: ns-1296.awsdns-34.org, ns-1833.awsdns-37.co.uk, ns-391.awsdns-48.com, and ns-731.awsdns-27.net. 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 4me.qa is handled by amazonaws.com with 1 MX records configured: inbound-smtp.eu-west-1.amazonaws.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 (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 4me.qa. 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 23 active subdomains for 4me.qa: admin.4me.qa, api.4me.qa, app.4me.qa, apps.4me.qa, blog.4me.qa, community.4me.qa, dev.4me.qa, and developers.4me.qa. Plus 15 additional subdomains. Active subdomains can reveal the organization's infrastructure, including development environments, API endpoints, and third-party service integrations.

The title tag for 4me.qa is well-optimized at 58 characters: "Xurrent | ITxM: AI-Powered Service and Incident Management". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 216 characters (slightly long): "AI-powered service and operations management, built for the modern enterprise. Xurrent unifies ITSM, ESM, and ITOM in on...". 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.xurrent.com/, preventing duplicate content issues, 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 ("Xurrent | ITxM: AI-Powered Service and Incident Management..."), 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_large_image is configured, which controls how links appear when shared on Twitter/X. The "summary_large_image" type displays a large image preview, which typically generates higher engagement rates than the basic card type.