Is rogers.com a scam site? Scam, spam & reviews

Score
96
HTTP status
200
https://www.rogers.com/
SSL/TLS
Valid
2026-04-14T23:59:59+00:00
Server/AS
MICROSOFT-CORP-MSN-AS-BLOCK, US
2.23.109.22
Open site

Scores & key points

Security
Reputation
Scam risk

Caution signals

No clear warnings detected.

Reputation

Open PageRank 5.60 / 10
Tranco 4900 Global
Source: top-1m.csv

Review summary — rogers.com

Overall 96 (Mostly safe)

Multiple security indicators are favorable and there are few major risk signals.

Strengths

  • Valid SSL/TLS certificate
  • HSTS enabled
  • CSP enabled
  • SPF configured
  • DMARC configured
  • Domain age ≥ 1 year

Weaknesses

Detailed review — rogers.com

Domain review

Domain created: 1992-05-15T04:00:00Z (≈ 33y 7m). Registrar: CSC Corporate Domains, Inc.. Hosting / AS: MICROSOFT-CORP-MSN-AS-BLOCK, US — Canada. Popularity: Tranco #4900, OPR 5.60/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC None. Certificate valid until: 2026-04-14T23:59:59+00:00.

Shop / transaction review

No mixed content detected. No mixed content detected. Structured data: Organization Absent, contactPoint Absent. Hidden text ratio 0%.

Technical review

HTTP 200 Success · Server MICROSOFT-CORP-MSN-AS-BLOCK, US. HSTS Off (preload: Unknown). Applies 5/6 security headers. DNSSEC Off. Email security: SPF On, DMARC None. MTA‑STS policy: None. TLS‑RPT Off. security.txt: not available. Missing cookie attributes: Secure×0 / HttpOnly×0 / SameSite×0. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.

Explanation — strengths and stability

Age: about (≈ 33y 7m) (created on 1992-05-15T04:00:00Z).

GSB clean

WebRisk clean

Certificate valid until: 2026-04-14T23:59:59+00:00.

Email security: SPF On, DMARC none.

Applies 5/6 security headers.

No mixed content detected.

Looking at operator information together with trust metrics helps you judge brand/merchant consistency and the likelihood of long‑term operation.

Checking payment page security (HTTPS enforcement, form target host consistency, script integrity) along with customer support and return policy gives a more accurate sense of real‑world trust.

In parallel, applying security headers, automated certificate renewal, email domain protection (DMARC/TLS‑RPT), and removing mixed content will improve overall reliability and delivery/search stability.

Explanation — risks and areas to improve

Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.

Without DNSSEC, trust relies solely on parent name servers and DNS tampering risks can be higher in some environments.

If DMARC is absent or set to p=none, protection against sender spoofing is weak. Consider quarantine/reject policies.

Without MTA‑STS, SMTP TLS enforcement is weaker.

Without TLS‑RPT, it is harder to collect TLS failure signals and operational insight.

Without security.txt, the vulnerability disclosure channel is unclear and response may be delayed.

Estimated domain age
33y 7m
Registrar
CSC Corporate Domains, Inc.
SSL valid
Yes
SSL expires
2026-04-14T23:59:59+00:00
HTTP status
200
Server / ASN
MICROSOFT-CORP-MSN-AS-BLOCK, US
Final URL
https://www.rogers.com/
SPF
Yes
DMARC
Yes
CT wildcard usage
No
HSTS preload
Unknown
security.txt
No
TLS‑RPT receivers
Absent
Domain creation date
1992-05-15T04:00:00Z
Hosting / AS
MICROSOFT-CORP-MSN-AS-BLOCK
Hosting country
Canada
GSB status
No match
WebRisk status
No match
DMARC policy
None
DNSSEC
Absent
Legal/contact pages
No
Structured data: Organization
Absent
Structured data: contactPoint
Absent
Registry risk (0–100)
5
dmarc_p
None
dmarc_rua
mailto:dreports_rogers@shaw.ca
dmarc_ruf
mailto:dforensic_rogers@shaw.ca
mixed_http
0
cookie_no_secure
0
cookie_no_httponly
0
cookie_no_samesite
0
JS obfuscation score
0
Payment logo count
0
Hidden text ratio (%)
0
Cross‑domain POST form count
0
External host logos/icons
0
YARA matches
0

This analysis is an automated, data‑based opinion for reference only. Please verify the information yourself before paying or downloading anything.

About this report

  • First analysis: -
  • Last updated: 2025-12-03 10:22:03
Email

Traffic signals

UTM source -
UTM medium -
ref / from -
Shortened URLs on page 0

Performance

Field LCP-ms
Field INP-ms
Field CLS-
Lab LCP-ms
Lab TBT-ms
Mobile score-
Mobile measurement error: request_failed
Lab LCP-ms
Lab TBT-ms
Desktop score-
Desktop measurement error: request_failed
https://www.rogers.com/

Security headers

  • HSTS
  • Content‑Security‑Policy
  • X‑Content‑Type‑Options
  • X‑Frame‑Options
  • Referrer‑Policy
  • Permissions‑Policy
Set Referrer‑Policy
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

Domain lineage

  1. 1992-05-15
    Domain registered: 1992-05-15T04:00:00Z

Essentials

Google Safe Browsing No match
Google Web Risk No match
AbuseIPDB -
SPF Configured
DMARC none
DNSSEC No
Cookie security No issues detected
Mixed content (http) 0
Legal pages Absent
DMARC details
DMARC policy (p): none
Aggregate reports (rua): mailto:dreports_rogers@shaw.ca
Failure reports (ruf): mailto:dforensic_rogers@shaw.ca
TXT: v=DMARC1;p=none;pct=100;rua=mailto:dreports_rogers@shaw.ca;ruf=mailto:dforensic_rogers@shaw.cav=DMARC1;p=none;pct=100;rua=mailto:dreports_rogers@shaw.ca;ruf=mailto:dforensic_rogers@shaw.ca
HTTP status200
Server MICROSOFT-CORP-MSN-AS-BLOCK, US
CDN / Hosting Other CDN
HSTSNo
Valid until2026-04-14T23:59:59+00:00
IssuerDigiCert Inc / DigiCert TLS RSA SHA256 2020 CA1
Registrant / organizationMICROSOFT-CORP-MSN-AS-BLOCK, US
RegistrarCSC Corporate Domains, Inc.
ASN8075
Network20.160.0.0/12
TitleMobile, Internet, TV, Home Monitoring, Home phone - Rogers
Final URL: https://www.rogers.com/

Threat insight

Mostly safe (risk 0/100)
  • Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
  • Suspicious JavaScript patterns detected

The risk score of this site is calculated by combining browser security headers, SSL status, mixed content, email domain protection (SPF/DMARC), redirect/obfuscation patterns, and the results of Google Safe Browsing and WebRisk. There are currently few clear signs of malicious behavior, but insufficient security headers or email protection can increase the risk of phishing or man‑in‑the‑middle attacks. Before entering important information, re‑check the domain spelling and how you reached the site (ads, DMs, shortened URLs, etc.). Before entering payment or personal information, verify operator information (company/contact), HTTPS enforcement, DMARC/TLS‑RPT, and check for mixed content.

Deep scan (HTML / headers)

Mostly safe (deep 30/100)
  • Suspicious JavaScript obfuscation patterns have been observed.
  • Some cookie security attributes (Secure/HttpOnly/SameSite) are missing.

If unexpected popups, wallet connection requests, or download prompts appear, cancel once and re‑check via official announcements or community channels. For session/login cookies, always set Secure, HttpOnly, and SameSite.

HTTP status (deep) 200
Set‑Cookie (count) 6
Cookie security insufficient Secure×1 / HttpOnly×3 / SameSite×4
HTTP resources (deep) 0
Top third‑party hosts 3
Suspicious JS patterns 1
Collection time: 2025-12-03T10:22:03+00:00
images.ctfassets.net rogers.com assets.rogers-assets.com
Set‑Cookie (samples)
country=KR; path=/; domain=.rogers.com; secure</code><br><code>adobe_network_info={"asn":"16509","network":"aws","network-type":"hosted","bandwidth":"5000","country":"KR","province":"FALSE"}; path=/; domain=.rogers.com; secure</code><br><code>_analyticsUUID=bcc2e8eb-61b2-413b-8221-47784a523cac; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.rogers.com; secure; HttpOnly; SameSite=None</code><br><code>_analyticsUUID2=bcc2e8eb-61b2-413b-8221-47784a523cac; expires=Mon, 31-Dec-2038 23:59:59 GMT; domain=.rogers.com</code><br><code>ALB-Rogers-Browse=Prod-A; path=/; secure; HttpOnly</code><br><code>akavpau_browse_en=1764757923~id=cfaf756224a1a4a31e732826afee74bc; Path=/; HttpOnly; Secure; SameSite=None

Social

  • X

Platforms that this site may be using.

User scenarios

If you make a payment on this site

No strong malicious signs were found, but online payments always carry some risk. Double-check the amount, payee and refund policy before you pay.

If you log in or enter personal data

No clear malicious patterns were found, but treat passwords and 2FA codes as highly sensitive. Avoid reusing passwords across sites. Missing cookie security attributes or cross-domain POST forms can make sessions easier to steal or misuse. After logging in, watch for unusual account or billing activity.

Server location

Canada (CA) · ASN 8075 / MICROSOFT-CORP-MSN-AS-BLOCK

History

Change --

Recently added sites

Reviews

Average - / total 0

Checksum 3077ca542a2765399841f421209ac07e71ab6c1609450a9856700cacff0b6c2c

Analyzing

Collecting various signals and public data.

  1. Start
  2. Fetch DNS / WHOIS
  3. Check HTTP response
  4. Verify SSL/TLS
  5. Query reputation
  6. Collect PageSpeed data
  7. Analyze security headers
  8. Check email security
  9. Integrate extended signals
  10. Build report