Skip to main content

Security report for majestic12.co.uk

Majestic-12 · Technology · United Kingdom

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

65/100

Risk levelMedium

0–100, higher is better. How it is calculated

Majestic-12 is a niche distributed search engine project based in the United Kingdom, focused on creating a web search engine through distributed computing principles similar to SETI@home. The website provides downloadable node software for participants to contribute to web crawling and indexing efforts. The project also offers SEO-related services. The website content is technical and community-oriented, with a history of updates dating back to 2007, indicating a long-standing initiative. However, the domain WHOIS data is unavailable or indicates the domain is invalid under Nominet UK rules, which raises questions about domain legitimacy or usage of a non-standard domain name. Technically, the website uses basic HTML, CSS, and JavaScript without modern frameworks or CMS. The site lacks HTTPS enforcement, with the search form submitting data over HTTP, which is a security concern. Mobile optimization and accessibility are poor, and no analytics or tracking scripts are detected, indicating minimal user tracking. The site lacks privacy, cookie, and terms of service policies, which impacts privacy compliance. From a security perspective, the absence of HTTPS and security headers reduces the security posture. No sensitive data exposure or vulnerable libraries were detected in the HTML content. The site does not provide contact information or incident response channels, limiting transparency and user trust. Overall, the security maturity is low to moderate. The overall risk assessment suggests that while the project appears legitimate and community-driven, the domain registration issues and lack of security best practices present risks. Strategic recommendations include implementing HTTPS, adding security headers, improving privacy compliance with policies, enhancing mobile usability, and clarifying domain registration status to improve trust and security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. 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.

Priority findings

7 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching majestic12.co.uk

This scan found 23 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

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

SSL/TLS
67
Security headers
15
Email security
88
DNS health
70
Network security
100
GDPR outside view
50
Average
65

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

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.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

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

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention majestic12.co.uk, from OffSeq Breach.

Total records
28
Employees
0
Customers
28
Third parties
0
Weak passwords
61%

2 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for majestic12.co.uk.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Majestic-12 operates as a small technology project focused on distributed web crawling and search engine development. Its competitive advantage lies in leveraging distributed computing contributed by a global community of participants running MJ12node software. The business model is community-driven with optional SEO services. The target customer segments include technology enthusiasts, SEO professionals, and distributed computing participants. The project has a long history with consistent updates and community engagement through forums and blogs. Partnerships include server donations from companies like Gigaserver.nl. Growth indicators include milestone achievements such as crawling over one trillion URLs. However, the lack of formal business registration data and domain registration irregularities may limit commercial scalability and trust among enterprise customers.

Security posture

The website's security posture is limited by the absence of HTTPS, which exposes user interactions such as search queries to potential interception. No security headers are present to mitigate common web attacks. The site does not collect sensitive user data via forms, reducing exposure risk. There is no evidence of compliance with GDPR or other data protection regulations, as privacy and cookie policies are missing. Incident response mechanisms and security contact channels are not provided, limiting the ability to report or respond to security incidents. The lack of analytics and tracking reduces privacy concerns but also limits insight into user behavior. Overall, the security maturity is low, and improvements are needed to protect users and enhance trust.

Recommendations

  1. Implement HTTPS across the entire website with a valid SSL certificate to secure all user interactions.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web vulnerabilities.
  3. Develop and publish comprehensive privacy and cookie policies to comply with GDPR and inform users about data handling practices.
  4. Improve mobile optimization and accessibility to enhance user experience across devices.
  5. Clarify domain registration status and ensure domain legitimacy to improve trust and reduce suspicion.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Majestic-12
Description
Majestic-12 is a distributed search engine project aiming to create a web search engine using distributed workload concepts similar to SETI@home and distributed.net. The project includes software nodes (MJ12node) for crawling and indexing the web, with a focus on open participation and distributed computing.
Key services
Distributed web crawling and indexing, Search engine functionality, SEO services
Content quality
good
Branding
moderate

Technology

Stack
HTML, CSS, JavaScript
Performance
moderate
Mobile
poor
Accessibility
basic
SEO
basic

Security

Observed score
40/100
Good practices seen
  • No visible forms collecting sensitive data
  • No exposed credentials or sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
good
Navigation
good
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website is accessible with full content and no WAF blocking
  2. No privacy, cookie, or terms of service policies found
  3. No contact emails or phone numbers explicitly provided
  4. Search form uses HTTP action URL, not HTTPS
  5. Website content is technical and project-focused with detailed news and stats
  6. No modern frameworks or CMS detected
  7. Mobile optimization is poor
  8. No analytics or tracking scripts detected
  9. No social media links found
  10. WHOIS data is missing or invalid for the domain
Technical notes

Notes

The website is built using basic HTML, CSS, and JavaScript without modern frameworks or CMS. The search form uses an HTTP action URL, which is insecure. There is no evidence of performance optimization or mobile responsiveness. The site lacks analytics and tracking scripts, indicating minimal data collection. Hosting provider details are not discernible from the content. The site structure is clear with navigation links to projects, forums, blogs, and downloads. Technical debt is indicated by outdated design and lack of modern web standards. Modernization opportunities include adopting HTTPS, responsive design, and accessibility improvements. Technical risks include potential data interception due to lack of encryption and limited security controls.
Standards and sources

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

Reviews of this site

Share your experience with majestic12.co.uk. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review majestic12.co.uk.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.