rp02.net

We performed a comprehensive analysis of rp02.net on 2026-07-04. The website returned an HTTP 200 status code with a server response time of 8187ms. The page is served over HTTP/1.1 protocol with Gzip compression enabled, achieving approximately 60.0% size reduction. The total page weight is 14 KB. 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 100/100 (excellent). The following security headers are properly configured: Content-Security-Policy, Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. All recommended security headers are in place, providing comprehensive protection against common web attacks. Our technology detection scan identified 1 technologies across 1 categories powering rp02.net. The detected stack includes Google Fonts. Based on our comprehensive analysis of domain age, SSL configuration, email authentication, security headers, and blacklist status, rp02.net receives an overall trust score of 73/100, classified as "Likely Safe".

After conducting a thorough safety and legitimacy analysis, rp02.net receives a trust score of 73/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, and DMARC email authentication with a quarantine policy. 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 rp02.net 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 rp02.net 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. Fonts: Google Fonts — delivers web fonts for typography for rp02.net.

rp02.net delivers its homepage in 8187ms (server response time), which is considered slow by industry standards. The total page weight is 14 KB, and we detected 56 resource requests loading assets from 13 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 3 CSS files and 0 out of 1 JavaScript files are minified. Minifying the remaining 4 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 rp02.net produces approximately 0.01g 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 14 KB is the primary factor in this calculation. Core Web Vitals data from the Chrome User Experience Report (CrUX) is not available for rp02.net. 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.

rp02.net resolves to the IPv4 address 185.75.141.195, 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 2 name servers: ns1.sarbacane-dns.com and ns2.sarbacane-dns.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 rp02.net is handled by customizedurl.com with 1 MX records configured: mx.customizedurl.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 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 not enabled for rp02.net. 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 homepage of rp02.net contains 312 words of visible text content. This is a moderate amount of content. The page is structured with 4 H2 headings, 0 H3 headings, 0 H4 headings. The page includes 23 images. 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 2 internal links pointing to other pages on the same domain and 20 external links pointing to third-party websites. There are 1 external JavaScript files, 3 CSS stylesheets, and 0 iframes on the page. The site implements the following web standards and features: Progressive Web App (PWA) manifest (enabling app-like installation). 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 4 platforms: Facebook (@SarbacaneSoftware), Twitter (@sarbacaneSoft), Instagram (@sarbacanesoftware), and Linkedin (@sarbacane-positive). An active social media presence is a positive trust indicator and helps build brand awareness and customer engagement.

The title tag for rp02.net is well-optimized at 45 characters: "Signaler un abus email | Postmaster Sarbacane". The length falls within the ideal range for Google search results, ensuring the full title is displayed without truncation. The meta description is 149 characters (well-optimized): "Recevez-vous un email indésirable d'un utilisateur Sarbacane ? Signalez tout abus ou non-respect des règles en nous cont...". 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 fr, the meta robots directive is set to noindex, nofollow, and a favicon is configured. No Open Graph tags are configured. When someone shares a link to rp02.net on social media, the platform will have to guess the title, description, and image — often producing unattractive or inaccurate previews. Adding OG tags is essential for social media marketing.