CheckMySource · Technology
Low risk. No critical or high findings.
CheckMySource is a small technology company operating a crowd-sourced platform that provides safety reports on websites based on user feedback for specific activities such as logging in, paying, uploading files, and writing notes. The service emphasizes transparency by showing raw counts behind verdicts and does not require user accounts for lookup or reporting, positioning itself as a niche community-driven website safety resource. The website is well designed with good mobile optimization and accessibility, offering a clear and professional user experience. Technically, the site uses modern web standards including HTML5, CSS3, JavaScript, and web manifest files, though no major frameworks or CMS are detected. Security posture is moderate with HTTPS implied but lacking explicit security headers and published security policies. Privacy compliance is basic with a privacy policy present but no cookie consent mechanism or GDPR compliance indicators. Business credibility is supported by transparent operations and no paid ratings, but contact information is limited to a web form without direct emails or phone numbers. Overall, the site is trustworthy and safe with no adult or questionable content detected.
Scanned
NIS2 Art. 21(2)
The NIS2 figure counts only evidence anyone can see from the internet. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.
GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.
No critical or high findings. These medium findings are worth fixing next.
TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.
The server still accepts TLS 1.1 and TLS 1.0, deprecated by RFC 8996. Modern browsers no longer use them, but they let outdated clients connect with weak cryptography.
What to do: Disable TLS 1.0 and 1.1; keep TLS 1.2 and TLS 1.3 (in CDN dashboards this is the "minimum TLS version" setting).
This scan found 8 issues across 4 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
€25per month
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. See sample alerts.
€39.90one-time
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Each check with its score, findings and the evidence it collected.
The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.
Counted in this score
Not counted
Findings that cap the score at 49
Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.
Partial scans
When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.
Risk levels
Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.
Leaked records that mention checkmysource.com, from OffSeq Breach.
No leaked records found
Breach holds no records for checkmysource.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Automated reading of the public site. Ratings are indicative.
Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.
Retrieved 2026-10-25
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with checkmysource.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review checkmysource.com.