Is backlog.com a scam site? Scam, spam & reviews
Scores & key points
Caution signals ⓘ
No clear warnings detected.
Reputation
Review summary — backlog.com
Overall 91 (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 — backlog.com
Domain review
Domain created: 2001-06-02T10:30:51Z (≈ 24y 6m). Registrar: Amazon Registrar, Inc.. Hosting / AS: AMAZON-02, US — United States. Popularity: Tranco #86530, OPR 5.78/10. Reputation: GSB clean WebRisk clean. Email security: SPF On, DMARC None. Certificate valid until: 2026-05-25T23: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 301 Redirect · Server AMAZON-02, 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. JS obfuscation score 0. Reputation: GSB clean, WebRisk clean → overall Good.
Explanation — strengths and stability
Age: about (≈ 24y 6m) (created on 2001-06-02T10:30:51Z).
GSB clean
WebRisk clean
Certificate valid until: 2026-05-25T23: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.
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-11-30 05:58:58
Claim website ownership
Traffic signals
Performance
Security headers
- HSTS ⓘ
- Content‑Security‑Policy ⓘ
- X‑Content‑Type‑Options ⓘ
- X‑Frame‑Options ⓘ
- Referrer‑Policy ⓘ
- Permissions‑Policy ⓘ
add_header Permissions-Policy "geolocation=(); microphone=(); camera=()" always;
Domain lineage
-
2001-06-02Domain registered: 2001-06-02T10:30:51Z
Essentials
DMARC details
v=DMARC1; p=none; fo=1; rua=mailto:e5b181af@mxtoolbox.dmarc-report.com; ruf=mailto:e5b181af@forensics.dmarc-report.com;v=DMARC1; p=none; fo=1; rua=mailto:e5b181af@mxtoolbox.dmarc-report.com; ruf=mailto:e5b181af@forensics.dmarc-report.com;Threat insight
- Without HSTS, downgrade and man‑in‑the‑middle attacks can weaken HTTPS enforcement. Enable HSTS and prepare for preload registration.
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)
Before entering payment or personal information, verify the site operator/contact, HTTPS enforcement (HSTS), and the presence of DMARC and TLS‑RPT.
Iframe hosts
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.
Server location ⓘ
History
Change ⓘ --Recently added sites
Reviews
Average - / total 0
Checksum a3a324b887ed9f0f21a76d75c757b6337bfbdadc23921237d80c24fd7710bc25