Skip to main content

Security report for portlandmercury.com

Portland Mercury · Media · United States

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

Security score

67/100

Risk levelMedium

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

Portland Mercury is a local alternative weekly newspaper focused on news, entertainment, and cultural events in Portland, Oregon. The website provides coverage of local news, politics, music, film, arts, and community events, targeting a general audience interested in Portland's cultural scene. The business operates primarily as a media publication with a focus on local content and event listings. Technically, the website employs modern web technologies including jQuery, Bootstrap, Font Awesome, Google Tag Manager, and Facebook SDK, indicating a moderate level of digital maturity. The site appears to be mobile optimized with good SEO practices but lacks explicit CMS identification and hosting details. Security posture is moderate with HTTPS usage implied but no explicit security headers or published security policies detected. Tracking technologies such as Google Analytics and Facebook Pixel are used, but privacy compliance is weak due to the absence of privacy and cookie policies. Overall, the site is legitimate and consistent with a local media outlet but would benefit from enhanced privacy and security disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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

5 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 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 Cookie Policy found

      GDPR requires clear information about cookie usage

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching portlandmercury.com

This scan found 26 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
77
Security headers
25
Email security
70
DNS health
75
Network security
100
GDPR outside view
53
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

Portland Mercury holds a niche position as an alternative weekly newspaper serving Portland's local community. Its competitive advantage lies in its focus on local news and entertainment, providing curated content such as event calendars and restaurant listings. The business model is content-driven, likely supported by advertising and sponsored content. The target customer segment includes residents and visitors interested in Portland's cultural and entertainment offerings. There is no evidence of parent or subsidiary companies from the provided data. The partnership ecosystem includes social media platforms like Facebook and Twitter for audience engagement. Growth indicators are not explicitly available, but the use of modern tracking and marketing tools suggests ongoing digital engagement efforts.

Security posture

The website demonstrates a basic to moderate security maturity level. HTTPS is used, ensuring encrypted communications. However, no explicit security headers such as Content-Security-Policy or X-Frame-Options were detected, which could improve protection against common web attacks. There is no published security policy or incident response information, which limits transparency and preparedness communication. No vulnerability disclosures or security.txt files were found, indicating a lack of formal vulnerability management communication. Tracking scripts from Google and Facebook are present, but privacy compliance is weak due to missing privacy and cookie policies. No exposed sensitive data or vulnerable libraries were identified in the provided content. Overall, the security posture is adequate for a media website but could be improved with better security practices and transparency.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  2. Implement and configure security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a security policy and incident response contact information to enhance transparency and preparedness.
  4. Introduce a vulnerability disclosure program or security.txt file to facilitate responsible reporting.
  5. Ensure all forms and user inputs have proper security controls including CSRF protection and input validation.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Portland Mercury
Description
Portland Mercury covers Portland news, politics, music, film, and arts; plus movie times, club calendars, restaurant listings, forums, blogs, and Savage Love.
Key services
news coverage, entertainment listings, event calendars, restaurant listings, forums and blogs
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.6.0, Bootstrap 5.1.3, Font Awesome 6 Pro, Google Tag Manager, Facebook SDK
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS usage implied by URL
  • Use of Google Tag Manager and Facebook SDK scripts

Analytics and tracking

Services
Google Analytics, Facebook Pixel
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel, Google Analytics (via GTM)
Marketing tools
Facebook SDK
Transparency
basic

Site quality

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

Key observations

  1. Website is a local alternative weekly newspaper for Portland, Oregon.
  2. No explicit privacy, cookie, or terms of service policies found in the provided content.
  3. Uses common web technologies and tracking scripts.
  4. No security policy or incident response information published.
  5. No contact emails or phone numbers explicitly found in the provided HTML snippet.
  6. No forms detected in the provided content.
  7. No security headers explicitly detected in the provided data.
  8. Content is appropriate for general audiences with no adult content.
Technical notes

Notes

The website uses a combination of jQuery 3.6.0, Bootstrap 5.1.3, and Font Awesome 6 Pro for UI and iconography, indicating a modern frontend stack. Google Tag Manager and Facebook SDK are used for analytics and marketing, showing integration with major tracking platforms. The site loads external fonts and scripts from reputable CDNs. Performance is moderate with asynchronous loading of scripts. Mobile optimization is good, supported by responsive meta tags and Bootstrap. Accessibility is basic, with no explicit ARIA or accessibility features detected in the snippet. SEO is supported by proper meta tags including Open Graph and Twitter cards. No CMS or hosting provider information was identified. Technical risks include lack of security headers and missing privacy disclosures.
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. 67/100Medium34 findingsView report
Reviews of this site

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