Digital exposure report
samba.tv
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-21 09:50 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://samba.tv/ | grep -i "Content-Security-Policy"
- 2.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS samba.tv
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- samba.tv
- Website request
- GET https://samba.tv/
- Scan time
- 2026-11-21 09:50:10 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 28/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 11/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumClickjacking protection · Hardening gap+5
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.MediumCSP — protection from script injection · Hardening gap+8
- 4.LowReferrer-Policy · Hardening gap+3
- 5.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 5 of the 10 allowed DNS lookups.
v=spf1 include:mg-spf.greenhouse.io include:spf.mandrillapp.com include:_spf.google.com include:spf.salesforce.com include:2164593.spf08.hubspotemail.net ip4:216.183.117.71 ip4:35.80.141.6 ip4:44.229.121.55 -all
$ dig +short TXT samba.tv
DMARC — anti-spoofing policy
Passed · Severity: OK · 13/15Forged email in the company's name is sent to the spam folder.
Policy p=quarantine. p=quarantine — consider moving to p=reject.
v=DMARC1; p=quarantine; rua=mailto:postmaster@samba.tv; aspf=s;
$ dig +short TXT _dmarc.samba.tv
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: google. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCezq5HfOq1WmMlejV7qHmkSMTScYR1eGLp…
$ dig +short TXT google._domainkey.samba.tv
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 smtp.google.com
$ dig +short MX samba.tv
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://samba.tv/ returned HTTP 200 (final URL: https://samba.tv/). Client-side certificate validation passed.
HTTP 200 Final URL: https://samba.tv/
$ curl -sIL https://samba.tv/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 308 → https://samba.tv/
HTTP 308 Location: https://samba.tv/
$ curl -sI http://samba.tv/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: Let's Encrypt, expiring 2027-01-09 (48 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: Let's Encrypt Valid from: 2026-10-11 Valid until: 2027-01-09 Names: samba.tv Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect samba.tv:443 -servername samba.tv 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 7/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000
$ curl -sIL https://samba.tv/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://samba.tv/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Failed · Severity: Medium · Hardening gap · 0/5Missing X-Frame-Options / frame-ancestors: this removes one layer of protection against clickjacking.
No valid X-Frame-Options and no frame-ancestors in the CSP.
X-Frame-Options: (missing)
$ curl -sIL https://samba.tv/ | grep -i "X-Frame-Options"
- Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
- Also set frame-ancestors in the CSP — the modern alternative.
/* X-Frame-Options: SAMEORIGIN
Safety: This change is made in your server/CDN settings. Test on staging before production. If partners embed the site in an iframe, add them to frame-ancestors instead of using DENY.
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://samba.tv/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://samba.tv/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://samba.tv/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://samba.tv/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS samba.tv: NODATA
$ dig +short DS samba.tv
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec samba.tv SOA delv samba.tv
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog"
0 issue "amazon.com" 0 issue "amazonaws.com" 0 issue "amazontrust.com" 0 issue "awstrust.com" 0 issue "godaddy.com" 0 issue "letsencrypt.org" 0 issue "pki.goog"
$ dig +short CAA samba.tv
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
4 NS servers.
ns-1094.awsdns-08.org ns-1787.awsdns-31.co.uk ns-297.awsdns-37.com ns-951.awsdns-54.net
$ dig +short NS samba.tv
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rulesNo gaps observed
- PCI DSS v4.02 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline2 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | samba.tv | 31.43.161.6 | 31.43.160.6 |
| AAAA | samba.tv | — |
| MX | samba.tv | 1 smtp.google.com |
| NS | samba.tv | ns-1094.awsdns-08.org | ns-1787.awsdns-31.co.uk | ns-297.awsdns-37.com | ns-951.awsdns-54.net |
| TXT | samba.tv | 1tnbgkdrp6krc2mf1uq8jse2k7 | 75042l71d1wrb8wph024q3lwxg67h99f | 963jout453fpgo6i048k5e0f9a | adobe-sign-verification=80d89a13f53e736ea6aff649423cc4a8 | anthropic-domain-verification-5cjvqs=tVtW5K5ZZHuJxlTSY2WRknMWb | apple-domain-verification=TxWiTAutkethn2TQ | atlassian-domain-verification=gRd7sdcK/NLHCkNVDfBDYS6rXay4sfsGrURotpeLD8ImIaOf4Au8Sr4lnPTVAzy7 | cursor-domain-verification-pj7scd=mZlUo7j2xfDFPODWvyKjZt7gM | google-site-verification=47o7LSxsiF1XJnOTGNpcAzS20bX-4sl62xOflQgxSjc | google-site-verification=Nbl1wsSCH5zJlTXOGaN-z6MBydwQ3OxNTKWgJbYel3E | google-site-verification=ZZTMwKgv2mvPL_umKL0bG0o6Ki5Sp4iCN7X87xZzV-Y | google-site-verification=taa3_1iO5nVelsrD_uTvV0BItWMYfNqikJHwBWjS1B0 | kayak-domain-verification=bvF4V3u7ft2HqwgtrMk_zgC4sUlLM2Nw1dj-m1U_tULO6qwLeLiwaoCAoV25xMmc | liveramp-site-verification=_OfeflKrGUb87f8S2FOnwHMUggnH_2js5t3thOqQv-M | mixpanel-domain-verify=849f12ea-2ecc-4560-a133-8de948035966 | mojecertpl-site-verification-S2kjMpr1fsNKmgkIN4RFZC5xOqRfdpZC | onetrust-domain-verification=2ea89e9149b34a9cb26496fd47cc24d6 | proxy-ssl.webflow.com | rippling-domain-verification=26f82aec6519cc22 | v=spf1 include:mg-spf.greenhouse.io include:spf.mandrillapp.com include:_spf.google.com include:spf.salesforce.com include:2164593.spf08.hubspotemail.net ip4:216.183.117.71 ip4:35.80.141.6 ip4:44.229.121.55 -all |
| TXT | _dmarc.samba.tv | v=DMARC1; p=quarantine; rua=mailto:postmaster@samba.tv; aspf=s; |
| CAA | samba.tv | 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" |
| DS | samba.tv | — |