Skip to main content

Security report for digg.com

Technology · N/a

Medium risk. 7 critical or high findings in Security headers and GDPR outside view.

Security score

67/100

Risk levelMedium

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

The website reboot.digg.com appears to be a minimal landing or application page related to Digg, a known internet media company. The page title and meta description indicate it is branded as 'Digg Reboot' with a tagline positioning Digg as 'The front page of the internet, now with superpowers.' However, the actual HTML content is minimal, containing no visible text content, navigation, or business information. The site uses modern web technologies including React, FullStory for session replay analytics, and Plausible for privacy-focused analytics. There is no evidence of privacy or cookie policies, contact information, or terms of service on the page, which limits compliance and trust signals. No WHOIS data is available for the subdomain, which is expected since WHOIS queries apply to registered domains, not subdomains. No web application firewall or blocking mechanisms were detected, and the site appears accessible but minimal in content. Overall, the site demonstrates moderate technical maturity but lacks content and compliance transparency, resulting in a low security and trust posture.

Scanned

This is an earlier scan of digg.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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 digg.com

This scan found 22 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. The full timeline opens with your unlock code.

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
100
Security headers
15
Email security
70
DNS health
80
Network security
100
GDPR outside view
35
Average
67

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

Technical appendix

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

Business context

Business profile

The site is likely a product or feature landing page for Digg, targeting internet users familiar with Digg's brand. The business model appears to be media or content aggregation, but no direct business or service details are provided on this page. The lack of contact or legal information suggests this is not a primary business site but rather a subcomponent or marketing page. The use of advanced analytics tools indicates an interest in user behavior tracking and optimization. No partnerships or subsidiaries are indicated. The minimal content and lack of policies limit the ability to assess revenue streams or growth indicators.

Security posture

Security posture is limited by the absence of visible HTTPS confirmation and security headers in the provided data. The site uses third-party analytics scripts which may introduce privacy concerns if not properly managed. No forms or input fields are present, reducing attack surface but also limiting user interaction. The lack of privacy and cookie policies indicates non-compliance with GDPR and other privacy regulations. No incident response or security policy information is available. Overall, the security maturity is low with recommendations to improve transparency, implement security headers, and ensure HTTPS enforcement.

Recommendations

  1. Implement and prominently link privacy and cookie policies to improve compliance and user trust.
  2. Ensure HTTPS is enforced and security headers such as Content-Security-Policy and X-Frame-Options are configured.
  3. Add clear contact information and business details to enhance credibility and compliance.
  4. Review and audit third-party analytics scripts for privacy impact and data minimization.
  5. Develop a comprehensive security policy and incident response plan accessible to users.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Digg - The front page of the internet, now with superpowers
Content quality
poor
Branding
moderate

Technology

Stack
React, FullStory, Plausible Analytics, Geist Font, Google Fonts
Frameworks
React
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
30/100

Analytics and tracking

Services
FullStory, Plausible Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
FullStory, Plausible Analytics
Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is minimal with no visible text content or navigation.
  2. No privacy, cookie, or terms of service policies found on the page.
  3. No contact information or forms present.
  4. Uses modern JavaScript frameworks and analytics tools.
  5. No security headers or HTTPS status information available from provided data.
  6. No WHOIS data for subdomain as expected; main domain WHOIS not provided.
  7. No signs of WAF or blocking mechanisms detected.
  8. Tracking scripts from FullStory and Plausible indicate user behavior analytics.
  9. No visible business or legal information on the page.
Technical notes

Notes

The site is built using React and loads external fonts and analytics scripts asynchronously. The use of FullStory and Plausible indicates a focus on user experience analytics and privacy-aware tracking. The HTML is minimal with no visible content or navigation, suggesting this is a single-page application shell or placeholder. No CMS or hosting provider information is discernible. Performance is likely moderate given minimal content but could be improved with better content delivery and SEO optimization. Accessibility and mobile optimization are basic due to lack of content and structure. Technical debt appears low but modernization opportunities exist in adding compliance and security features.
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

Earlier scans of this domain

  1. 56/100 −12Medium29 findingsView report
  2. 68/100Medium34 findingsView report
Reviews of this site

Share your experience with digg.com. 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 digg.com.

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.