Skip to main content

Security report for smithsonian.com

Smithsonian Enterprises · Media · United States

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

Security score

66/100

Risk levelMedium

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

Smithsonian.com serves as the digital platform for Smithsonian Enterprises, offering a blend of retail shopping, award-winning editorial content, original television series, and travel experiences worldwide. The website targets a general audience interested in culture, education, and travel, leveraging the strong brand recognition of the Smithsonian Institution. The domain has been registered since 2001, reflecting a mature and established online presence consistent with the Smithsonian's reputation. Technically, the website employs a modern technology stack including Cloudflare for DNS and CDN services, Google Analytics, Facebook Pixel, Hotjar, and Google Tag Manager for analytics and marketing. The site demonstrates good mobile optimization and a professional design, although some SEO and accessibility features appear basic. Performance is moderate, with room for improvement in technical modernization and security hardening. From a security perspective, the site enforces HTTPS and uses domain status locks to prevent unauthorized changes. However, DNSSEC is not enabled, and no explicit security headers or incident response policies are visible in the provided content. The absence of privacy and cookie policies, as well as a consent mechanism, indicates gaps in privacy compliance. No vulnerabilities or exposed sensitive data were detected, but improvements in security transparency and compliance documentation are recommended. Overall, Smithsonian.com is a credible and professionally maintained website with a strong brand and business model. To enhance trust and compliance, it should publish clear privacy and cookie policies, implement consent mechanisms, enable DNSSEC, and adopt security best practices such as security headers and incident response disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 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 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 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching smithsonian.com

This scan found 24 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
65
Security headers
25
Email security
55
DNS health
80
Network security
100
GDPR outside view
68
Average
66

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

Smithsonian.com operates within the media sector, combining e-commerce with cultural and educational content. Its market position is strong due to the Smithsonian Institution's brand equity. The business model integrates product sales, content consumption, and travel services, targeting a broad demographic interested in culture and education. Revenue streams likely include retail sales, advertising, and travel bookings. The website leverages partnerships with major analytics and CDN providers but does not publicly disclose detailed business or compliance information. Growth indicators include sustained domain registration and use of advanced marketing tools. The partnership ecosystem includes major technology providers but no explicit business partners or subsidiaries were identified from the content.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and domain status protections in place. However, the lack of DNSSEC, security headers, and published security policies indicates room for improvement. No incident response contacts or vulnerability disclosure mechanisms were found, which could hinder timely handling of security events. The extensive use of third-party tracking scripts raises privacy concerns, especially without visible consent mechanisms. Compliance gaps with GDPR and other privacy regulations are evident due to missing privacy and cookie policies. The security culture appears focused on operational security but lacks transparency and user privacy safeguards.

Recommendations

  1. Publish comprehensive privacy and cookie policies prominently on the website.
  2. Implement a cookie consent mechanism to comply with GDPR and other privacy laws.
  3. Enable DNSSEC to enhance DNS security and prevent spoofing.
  4. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  5. Establish and publish incident response contact information and vulnerability disclosure procedures.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Smithsonian Enterprises
Description
Shop products, read award winning content, watch original television series, and travel worldwide.
Key services
Online shopping of Smithsonian products, Award-winning editorial content, Original television series, Travel experiences worldwide
Content quality
good
Branding
consistent

Technology

Stack
Cloudflare DNS and CDN, Google Analytics, Google Tag Manager, Facebook Pixel, Hotjar, Webtrends, Font Awesome Pro
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Services
Google Analytics, Webtrends, Hotjar
Tracking level
extensive
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel, Hotjar, ScorecardResearch
Marketing tools
Webtrends
Transparency
basic

Site quality

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

Key observations

  1. No explicit privacy, cookie, or terms of service policies found in the provided HTML snippet.
  2. Multiple tracking and analytics scripts are used, but no visible consent mechanism detected.
  3. No contact emails, phone numbers, or physical addresses explicitly found in the provided content.
  4. Strong use of reputable third-party services for analytics and CDN.
  5. No security.txt or vulnerability disclosure information found.
  6. No visible forms detected in the provided HTML snippet.
  7. No security headers explicitly visible in the provided data.
  8. DNSSEC not enabled, which is a potential security improvement area.
Technical notes

Notes

The website uses a robust set of modern technologies including Cloudflare CDN and DNS, Google Analytics, Facebook Pixel, Hotjar, and Google Tag Manager. The presence of Font Awesome Pro indicates attention to design aesthetics. However, no CMS or specific web frameworks were detected, suggesting a custom or proprietary platform. Performance is moderate with good mobile optimization but basic SEO and accessibility features. Technical debt may exist due to missing DNSSEC and security headers. Opportunities for modernization include adopting advanced SEO practices, improving accessibility compliance, and enhancing security configurations.
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 smithsonian.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 smithsonian.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.