Back to results

Digital exposure report

malam.com

High exposure. Significant weaknesses put the brand, customers and email at risk.

Scanned: 2026-11-19 02:59 UTC

Full coverage: every applicable check was assessed.

D
62/100

What to do first

  1. 1.

    Tell receiving mail servers how to treat fake email from your domain

    Without this policy, inboxes have less guidance for spotting messages that impersonate you.

    Who can fix it: Your email provider, together with whoever manages your DNS

    How to verify after the fix

    dig +short TXT _dmarc.malam.com
  2. 2.

    Tell browsers to always use the secure version

    Helps browsers use HTTPS on future visits after they have received the policy.

    Who can fix it: Your web host

    How to verify after the fix

    curl -sIL https://malam.com/ | grep -i "Strict-Transport-Security"

A starting point, not a security guarantee.

What this grade means

Tested hostname
malam.com
Website request
GET https://malam.com/ → https://www.malamteam.com/
Scan time
2026-11-19 02:59:44 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 security15/30Spoofing email in the company's name is possible in some cases.
Encryption & certificate25/25Traffic to the site is encrypted and the certificate is valid.
Browser protections19/30Some browser protections are missing.
DNS infrastructure3/15The domain's infrastructure lacks basic protections.

Fix priorities

  1. 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
  2. 2.HighDMARC — anti-spoofing policy · Hardening gap+15
  3. 3.MediumDNSSEC — signed DNS records · Hardening gap+7
  4. 4.LowCAA — who may issue certificates · Hardening gap+5
  5. 5.LowCSP — protection from script injection · Hardening gap+3

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 10/10

An authorized sender list is defined and mail from other servers is rejected.

Valid SPF record with -all. 4 of the 10 allowed DNS lookups.

Source data: DNS TXT malam.com
v=spf1 a mx include:_spf.activetrail.com include:spf.protection.outlook.com ip4:84.95.211.168 ip4:192.117.113.26 ip4:192.116.175.146 ip4:91.195.162.18 ip4:62.219.95.156 ip4:62.219.95.95 ip4:91.195.162.147 ip4:91.195.162.5 ip4:91.195.162.6 -all
$ dig +short TXT malam.com
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Failed · Severity: High · Hardening gap · 0/15

No policy tells mail servers to block forged email in the company's name — a common opening for CEO fraud and phishing.

No TXT record at _dmarc.malam.com. Without DMARC, mail failing SPF/DKIM may still reach the inbox.

Source data: DNS TXT _dmarc.malam.com
(no DMARC record found)
$ dig +short TXT _dmarc.malam.com
Fix recommendation (effort: Medium)
  1. Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
  2. Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
  3. Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.malam.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@malam.com; fo=1"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.

Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Passed · Severity: OK · 5/5

A 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: selector1, selector2. Confirm signing with dkim=pass in a sent message's Authentication-Results.

Source data: DNS TXT <selector>._domainkey.malam.com
selector1._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCtR0yON4OhhWWx3RCoxAZTmPACVc3OgwEo…
selector2._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2EPUhU3su/CypVEMvfwETfT+8rtY…
$ dig +short TXT selector1._domainkey.malam.com
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail 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.

Source data: DNS MX malam.com
0 malam-com.mail.protection.outlook.com
$ dig +short MX malam.com
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Passed · Severity: OK · 10/10

The site loads over an encrypted connection.

https://malam.com/ returned HTTP 403 (final URL: https://www.malamteam.com/). Client-side certificate validation passed.

Source data: HTTPS GET https://malam.com/
HTTP 403
Final URL: https://www.malamteam.com/
$ curl -sIL https://malam.com/
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Passed · Severity: OK · 7/7

Visitors arriving at an unencrypted address are automatically sent to the secure version.

HTTP 301 → https://malam.com/

Source data: HTTP GET http://malam.com/ (redirects not followed)
HTTP 301
Location: https://malam.com/
$ curl -sI http://malam.com/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Passed · Severity: OK · 8/8

The certificate was accepted by a validating TLS client at scan time.

Live TLS handshake succeeded. No matching certificate details were available from CT logs; run the verify command to see the served certificate's dates.

Source data: Certificate Transparency logs (certspotter) for malam.com
Live TLS handshake: certificate accepted
The CT log service was unavailable at the time of the check
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect malam.com:443 -servername malam.com 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Failed · Severity: High · Hardening gap · 0/8

Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.

No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.

Source data: Response headers from https://www.malamteam.com/
Strict-Transport-Security: (missing)
$ curl -sIL https://malam.com/ | grep -i "Strict-Transport-Security"
Fix recommendation (effort: Easy)
  1. Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
  2. Gradually raise it to 31536000 (one year) and add includeSubDomains.
  3. Consider preload only once the policy is stable — removal from the preload list is slow.
/*
  Strict-Transport-Security: max-age=31536000; includeSubDomains

Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.

Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Needs attention · Severity: Low · Hardening gap · 5/8

A script policy exists, but it's permissive and offers only partial protection.

script-src includes: 'unsafe-eval' — weakens XSS protection.

Source data: Response headers from https://www.malamteam.com/
Content-Security-Policy: default-src 'none'; script-src 'nonce-jgNmONPvYCRJLXbPealRx3' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blob:; child-src 'self' https://challenges.cloudflare.com blob:; worker-src blob:; form-action http: https:; base-uri 'self'
$ curl -sIL https://malam.com/ | grep -i "Content-Security-Policy"
Fix recommendation (effort: Complex)
  1. First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
  2. Collect violations for a week or two and tune the policy to your legitimate sources.
  3. 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.

Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Passed · Severity: OK · 5/5

The site can't be embedded by foreign sites.

X-Frame-Options: SAMEORIGIN

Source data: Response headers from https://www.malamteam.com/
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://malam.com/ | grep -i "X-Frame-Options"
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Passed · Severity: OK · 4/4

The browser won't guess file types in a way that could execute code.

nosniff is set.

Source data: Response headers from https://www.malamteam.com/
X-Content-Type-Options: nosniff
$ curl -sIL https://malam.com/ | grep -i "X-Content-Type-Options"
Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Passed · Severity: OK · 3/3

Internal URLs don't leak to external sites.

Referrer-Policy: same-origin

Source data: Response headers from https://www.malamteam.com/
Referrer-Policy: same-origin
$ curl -sIL https://malam.com/ | grep -i "Referrer-Policy"
Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Passed · Severity: OK · 2/2

The site restricts access to sensitive browser features.

Permissions-Policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credential

Source data: Response headers from https://www.malamteam.com/
Permissions-Policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
$ curl -sIL https://malam.com/ | grep -i "Permissions-Policy"
Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Software version disclosure

Passed · Severity: OK · unscored

The server doesn't disclose software versions.

No version numbers found in the Server / X-Powered-By headers.

Source data: Response headers from https://www.malamteam.com/
server: cloudflare
x-powered-by: (missing)
$ curl -sIL https://malam.com/ | grep -iE "^(server|x-powered-by)"
Documentation: OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Needs attention · Severity: Medium · Hardening gap · 0/7

The 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.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = false
DS malam.com: NODATA
$ dig +short DS malam.com
Fix recommendation (effort: Medium)
  1. Enable DNSSEC at your DNS provider (one click at most providers).
  2. Copy the DS record your provider generates to your domain registrar.
  3. Wait for propagation and verify with DNSViz.
dig +dnssec malam.com SOA
delv malam.com

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.

Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Needs attention · Severity: Low · Hardening gap · 0/5

Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.

No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.

Source data: DNS CAA malam.com
(no CAA records found)
$ dig +short CAA malam.com
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
malam.com.  CAA  0 issue "letsencrypt.org"
malam.com.  CAA  0 iodef "mailto:security@malam.com"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.

Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

2 NS servers.

Source data: DNS NS malam.com
sdns.goldenlines.net.il
pdns.goldenlines.net.il
$ dig +short NS malam.com
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

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 rules1 observed gaps
  • PCI DSS v4.02 observed gaps
  • NIS2 / vendor due diligence4 observed gaps
  • SOC 2 / ISO 27001 baseline3 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

Amalam.com129.159.147.229
AAAAmalam.com—
MXmalam.com0 malam-com.mail.protection.outlook.com
NSmalam.comsdns.goldenlines.net.il | pdns.goldenlines.net.il
TXTmalam.come4_AjSd0i85bTQfNRoWGyZvXG0j8mPb4iceZYIGPwok | anthropic-domain-verification-s5qww1=0vZcUBLdouoq41CieTxFEa78D | MS=ms84887724 | 17osc4jco380cunb6kca1t62hd | MS=89CF9B5435B9E67880BB1A28099FF0637D80430D | google-site-verification=g06SmIhhinUiZESyUDdY7Qnq15V3YXTkHVv3vSK0Dt0 | MS=ms14195207 | XKx6ow0hTrM6oMj0TSvDo-Lk9AMWmdJYG32PEs01vnk | 3uo7ddpemhsfsje9ftovbm9v27 | d365mktkey=k1fulon6emj81iu8rxb8tgt0 | d365mktkey=2irnz7jzeus4tokad42mqsvim | itREMNUDjST5UbpydonyVg0G1b7nWxqW8g1sBPz4ts0 | v=spf1 a mx include:_spf.activetrail.com include:spf.protection.outlook.com ip4:84.95.211.168 ip4:192.117.113.26 ip4:192.116.175.146 ip4:91.195.162.18 ip4:62.219.95.156 ip4:62.219.95.95 ip4:91.195.162.147 ip4:91.195.162.5 ip4:91.195.162.6 -all | google-gws-recovery-domain-verification=70745108 | spycloud-domain-verification=be449f4a-c9bb-4761-9544-ab8471f136af
TXT_dmarc.malam.come4_AjSd0i85bTQfNRoWGyZvXG0j8mPb4iceZYIGPwok
CAAmalam.com—
DSmalam.com—
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain