Skip to main content

Is roeye.com a Scam? Security Check Results - roeye.com Reviews

R

Is roeye.com Safe? Security Analysis for ERROR: The request could not be satisfied

Check if roeye.com is a scam or legitimate. Free security scan and reviews.

OtherN/asmall
Analyzed 8/3/2025Completed 12:51:55 PM
54
Security Score
MEDIUM RISK

AI Summary

The website roeye.com is currently inaccessible due to a CloudFront 403 error indicating that requests are blocked, possibly due to traffic or configuration issues. This prevents any meaningful extraction of business, security, or compliance information from the site content. The domain is registered with Amazon Registrar, Inc. since 2008, indicating a mature domain age, but no registrant details or privacy protection are present. The lack of accessible content and security policies severely limits the ability to assess the company's market position, services, or compliance posture. Technically, the site is hosted on AWS infrastructure but lacks DNSSEC and visible security headers. The security posture cannot be evaluated due to the blocking mechanism. Overall, the site scores very low on content quality, technical implementation, security, privacy compliance, and business credibility due to inaccessibility.

🧠AI Business Intelligence

Technology stack, business insights, and market analysis powered by AI.

Business Intelligence

Market & Strategic Analysis

No business intelligence data could be extracted from the website due to the access block. The domain age suggests a potentially established entity, but no information about market positioning, business model, or partnerships is available. No contact details, certifications, or trust indicators are present. The domain uses AWS DNS services but no further technical or business ecosystem information is available.

Security Posture Analysis

Comprehensive Security Assessment

The security posture assessment is limited by the lack of accessible content. The domain does not have DNSSEC enabled, which is a recommended security practice. The site is protected by AWS CloudFront which is currently blocking access, indicating some level of security control. No security headers or SSL configuration details were found. No incident response or vulnerability disclosure information is available. Overall, the security maturity cannot be fully assessed but the blocking suggests some protective measures are in place.

Strategic Recommendations

Priority Actions for Security Improvement

1

Resolve the CloudFront 403 error to restore website accessibility for proper analysis and user access.

Observations

AI-powered comprehensive website and business analysis.

AI-Enhanced Website Analysis

CloudFront Detected

403 ERROR page generated by CloudFront indicating request blocked due to traffic or configuration error.

Analysis results may be incomplete. For accurate analysis, please contact guard@offseq.com

Business Insights

Content Quality:

poor

Branding:

inconsistent

Technical Stack

SEO:

poor

Security Assessment

0

Analytics & Tracking

Tracking Level:minimal
Privacy Compliance:poor

Advertising & Marketing

Transparency Level:poor

Website Quality Assessment

Design Quality:poor
User Experience:poor
Content Relevance:poor
Navigation Clarity:poor
Professionalism:poor
Trustworthiness:low

Key Observations

1

Website content is inaccessible due to a CloudFront 403 error.

🛡️Security Headers

HTTP security headers analysis and recommendations.

Security Headers

HTTP security headers analysis

15/100
Score

Missing Strict-Transport-Security header

HIGH

Forces HTTPS connections

Missing X-Frame-Options header

HIGH

Prevents clickjacking attacks

Missing X-Content-Type-Options header

MEDIUM

Prevents MIME type sniffing

Missing Content-Security-Policy header

HIGH

Controls resources the browser is allowed to load

Missing X-XSS-Protection header

MEDIUM

Legacy XSS protection (deprecated but still recommended)

Missing Referrer-Policy header

LOW

Controls referrer information sent with requests

Missing Permissions-Policy header

MEDIUM

Controls browser features and APIs

Sensitive data may be cached

LOW

Cache-Control header should include "no-store" for sensitive pages

👤GDPR Compliance

Privacy and data protection assessment under GDPR regulations.

GDPR Compliance

Privacy and data protection assessment

50/100
Score

No Privacy Policy found

HIGH

GDPR requires a clear and accessible privacy policy

No Cookie Policy found

HIGH

GDPR requires clear information about cookie usage

No Cookie Consent Banner found

HIGH

GDPR requires explicit consent for non-essential cookies

GDPR Compliance Analysis

Privacy Policy0% confidence
Cookie Policy0% confidence
Contact Information Found90% confidence
phone

🛡️NIS2 Compliance

Network & Information Security Directive compliance assessment.

NIS2 Compliance

Network & Information Security Directive

2/100
Score

No information security framework found

HIGH

NIS2 requires documented cybersecurity and information security measures

No vulnerability disclosure policy

MEDIUM

NIS2 encourages coordinated vulnerability disclosure

No security policy documentation found

HIGH

NIS2 requires documented cybersecurity governance and risk management

No incident response procedures found

HIGH

NIS2 requires documented incident response and business continuity plans

No business continuity planning found

MEDIUM

NIS2 emphasizes operational resilience and business continuity

No security contact information

HIGH

NIS2 requires clear incident reporting channels

No vulnerability reporting mechanism

MEDIUM

Clear vulnerability reporting supports coordinated disclosure

No NIS2 reference found

LOW

Consider explicitly mentioning NIS2 compliance efforts

Critical sector without clear security compliance

HIGH

Detected sectors: digital

📧Email Security

SPF, DKIM, and DMARC validation and email security assessment.

Email Security

SPF, DKIM, and DMARC validation

85/100
Score

No BIMI Record

LOW

BIMI displays brand logos in email clients

No MTA-STS Policy

MEDIUM

MTA-STS enforces TLS for email delivery

No TLS-RPT Record

LOW

TLS-RPT provides reporting for email TLS issues

SPF
Sender Policy Framework
DKIM
DomainKeys Identified Mail
DMARC
Domain-based Message Authentication
MX Records
Mail Exchange Records
BIMI
Brand Indicators
MTA-STS
Mail Transfer Agent Security
TLS-RPT
TLS Reporting
DNSSEC
DNS Security
SPF Details
Record:
v=spf1 include:mailgun.org include:amazonses.com ~all
DNS Lookups:2/10
Policy:~all
DKIM Selectors Found
Selector:selector2(1296-bit rsa)
DMARC Details
Policy:quarantine
Subdomain Policy:quarantine
Aggregate Reports:email_security_reports@roeye.com
Forensic Reports:email_security_reports@roeye.com

🏆SSL/TLS Security

Certificate validity and encryption analysis.

SSL/TLS Security

Certificate validity and encryption analysis

77/100
Score

Weak Protocols Supported

HIGH

Server supports weak protocols: TLSv1.1

OCSP Stapling Not Enabled

LOW

OCSP stapling improves performance and privacy

Certificate Transparency Not Implemented

LOW

Certificate is not logged in Certificate Transparency logs

Partial SSL/TLS Assessment

LOW

Completed 3 of 4 security checks due to time constraints

Protocol Support

TLSv1.3TLSv1.2TLSv1.1

OCSP Status

OCSP Stapling Disabled

📊DNS Health

DNS configuration and security assessment.

DNS Health

DNS configuration and security assessment

85/100
Score

DNSSEC Not Enabled

MEDIUM

DNSSEC is not configured for this domain

CAA Records Not Configured

LOW

Certificate Authority Authorization (CAA) records not found

DNS Records

A Records:18.165.122.102, 18.165.122.93, 18.165.122.66, 18.165.122.70
Name Servers:
ns-1302.awsdns-34.orgDNS only
ns-1962.awsdns-53.co.ukDNS only
ns-507.awsdns-63.comDNS only
ns-738.awsdns-28.netDNS only
MX Records:
10: inbound-smtp.eu-west-1.amazonaws.com
SOA:Serial: 1, TTL: 86400s

DNSSEC Status

DNSSEC Not Enabled

DNS Performance

Resolution Time:100ms

SPF Analysis

SPF Record:
v=spf1 include:mailgun.org include:amazonses.com ~all

Network Security

Port scanning and network exposure analysis.

Network Security

Port scanning and network exposure analysis

100/100
Score

Good Network Security Posture

LOW

No unnecessary services detected on common risky ports

🔧Technical Analysis

Detailed technical findings and analysis from AI assessment.

Technical Analysis

Comprehensive security assessment findings

Additional Findings

The website is hosted on AWS infrastructure with DNS managed by Amazon Registrar, Inc. The domain is mature, created in 2008, but DNSSEC is not enabled. The site currently returns a CloudFront 403 error blocking access, preventing analysis of the tech stack, CMS, or performance. No metadata, scripts, or forms are present in the accessible content. The lack of visible SEO or accessibility features suggests technical debt or misconfiguration. The hosting provider is reliable but the current configuration blocks legitimate access, which is a critical operational risk.
Analyze Another Website