Back to results

Digital exposure report

alahli.com

Good shape, with a few gaps worth closing this quarter.

Scanned: 2026-11-21 09:50 UTC

Partial coverage: the score is based on 40% of applicable check weight. 10 unverified check(s) are excluded, not counted as failures.

B
88/100

What to do first

  1. 1.

    Choose which companies may issue certificates for your domain

    This reduces the chance of a certificate being issued by a provider you did not choose.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short CAA alahli.com

A starting point, not a security guarantee.

What this grade means

Tested hostname
alahli.com
Website request
GET https://alahli.com/
Scan time
2026-11-21 09:50:12 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
  • DKIM — digital signature on email · Not detected (common selectors only)
  • HTTPS available · Unverified
  • HTTP → HTTPS redirect · Unverified
  • SSL/TLS certificate validity · Unverified
  • HSTS — enforce encryption in the browser · Unverified
  • CSP — protection from script injection · Unverified
  • Clickjacking protection · Unverified
  • X-Content-Type-Options · Unverified
  • Referrer-Policy · Unverified
  • Permissions-Policy · Unverified

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 security25/25Spoofing email from this domain is hard.
Encryption & certificate—Nothing in this category could be verified from public data.
Browser protections—Nothing in this category could be verified from public data.
DNS infrastructure10/15The domain's infrastructure works, but recommended hardening is missing.

Fix priorities

  1. 1.LowCAA — who may issue certificates · Hardening gap+13

To verify

Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.

  • HTTPS available
  • SSL/TLS certificate validity
  • CSP — protection from script injection
  • HSTS — enforce encryption in the browser
  • HTTP → HTTPS redirect
  • Clickjacking protection
  • DKIM — digital signature on email
  • X-Content-Type-Options
  • Referrer-Policy
  • Permissions-Policy

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. 0 of the 10 allowed DNS lookups.

Source data: DNS TXT alahli.com
v=spf1 ip4:213.5.172.11 ip4:213.5.172.12 ip4:213.5.172.70 ip4:213.5.171.70 ip4:213.5.172.40  ip4:213.5.172.41 ip4:95.140.163.19 ip4:95.140.163.20 ip4:95.140.163.21 ip4:95.140.163.40 ip4:95.140.163.41 ip4:66.159.232.92 ip4:143.55.149.242 -all
$ dig +short TXT alahli.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

Passed · Severity: OK · 15/15

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

Source data: DNS TXT _dmarc.alahli.com
v=DMARC1; p=reject; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:haseen@rua.dmarc.gov.sa; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com,mailto:haseen@ruf.dmarc.gov.sa; fo=1
$ dig +short TXT _dmarc.alahli.com
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

Not detected (common selectors only) · Severity: OK · Not scored

No DKIM key was found under the common selectors we probed. That doesn't mean DKIM is missing — selectors can't be listed from public DNS. Not scored.

A missing name for a probed selector (NXDOMAIN/NODATA) only means that selector isn't published. DKIM is marked unverified and excluded from the score. Check a sent message's Authentication-Results for dkim=pass and its s= selector.

Source data: DNS TXT <selector>._domainkey.alahli.com
Selectors checked: google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp — no key found
google._domainkey: nxdomain
selector1._domainkey: nxdomain
selector2._domainkey: nxdomain
default._domainkey: nxdomain
k1._domainkey: nxdomain
s1._domainkey: nxdomain
s2._domainkey: nxdomain
dkim._domainkey: nxdomain
mail._domainkey: nxdomain
smtp._domainkey: nxdomain
$ dig +short TXT google._domainkey.alahli.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.

4 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.

Source data: DNS MX alahli.com
10 mailgw5.alahli.com
10 mailgw6.alahli.com
40 mailgw1.alahli.com
40 mailgw2.alahli.com
$ dig +short MX alahli.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

Unverified · Severity: OK · Not scored

HTTPS couldn't be confirmed: the request timed out or the connection failed. This isn't treated as a security failure.

Requesting https://alahli.com/ didn't complete (HTTP 526). Timeouts and transport errors may be transient; the check is excluded from the score.

Source data: HTTPS GET https://alahli.com/
HTTP 526
$ curl -svI https://alahli.com/ 2>&1 | grep -E "SSL|HTTP|expire"
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

Unverified · Severity: OK · Not scored

Couldn't confirm whether plain HTTP redirects: port 80 didn't respond in time or the connection failed. Not scored.

Couldn't confirm whether plain HTTP redirects: port 80 didn't respond in time or the connection failed. Not scored.

Source data: HTTP GET http://alahli.com/ (redirects not followed)
Port 80 not responding (network)
$ curl -sI http://alahli.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

Unverified · Severity: OK · Not scored

The certificate couldn't be checked live because the HTTPS connection didn't complete. CT log data alone isn't used to score validity or expiry.

No live TLS evidence was obtained. CT entries are shown as context only. Not scored.

Source data: Certificate Transparency logs (certspotter) for alahli.com
CT logs (context only, not scored):
Issuer: Sectigo
Valid from: 2026-09-16
Valid until: 2027-04-02
Names: alahli.com, aqar.alahli.com, events.alahli.com, ifs.alahli.com, quickpay.alahli.com, uae.alahli.com
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect alahli.com:443 -servername alahli.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

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://alahli.com/
No HTTPS response received
$ curl -sIL https://alahli.com/
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

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://alahli.com/
No HTTPS response received
$ curl -sIL https://alahli.com/
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

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://alahli.com/
No HTTPS response received
$ curl -sIL https://alahli.com/
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

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://alahli.com/
No HTTPS response received
$ curl -sIL https://alahli.com/
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

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://alahli.com/
No HTTPS response received
$ curl -sIL https://alahli.com/
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

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://alahli.com/
No HTTPS response received
$ curl -sIL https://alahli.com/
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)

DNSSEC — signed DNS records

Passed · Severity: OK · 7/7

The domain's records are digitally signed and hard to forge.

An AD (Authenticated Data) flag was returned by a validating resolver.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = true
$ dig +dnssec alahli.com | grep -E "flags:.* ad"
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 alahli.com
(no CAA records found)
$ dig +short CAA alahli.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.
alahli.com.  CAA  0 issue "letsencrypt.org"
alahli.com.  CAA  0 iodef "mailto:security@alahli.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.

4 NS servers.

Source data: DNS NS alahli.com
ns0.alahli.com
ns1.alahli.com
ns2.alahli.com
ns5.alahli.com
$ dig +short NS alahli.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 unverified
  • PCI DSS v4.06 unverified
  • NIS2 / vendor due diligence1 observed gaps · 3 unverified
  • SOC 2 / ISO 27001 baseline6 unverified

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

Aalahli.com213.5.173.15 | 213.5.174.15
AAAAalahli.com—
MXalahli.com10 mailgw5.alahli.com | 10 mailgw6.alahli.com | 40 mailgw1.alahli.com | 40 mailgw2.alahli.com
NSalahli.comns0.alahli.com | ns1.alahli.com | ns2.alahli.com | ns5.alahli.com
TXTalahli.comMS=ms38063215 | google-site-verification=E0xf0n24M4dSPGSiSk6rfh98HOlC_vcLnVyVBxu2Hik | cisco-ci-domain-verification=2ac476b40ec6d290251114ce8d0f6f9c0cf27a879b57da16159f038bdfe8a844 | v=spf1 ip4:213.5.172.11 ip4:213.5.172.12 ip4:213.5.172.70 ip4:213.5.171.70 ip4:213.5.172.40 ip4:213.5.172.41 ip4:95.140.163.19 ip4:95.140.163.20 ip4:95.140.163.21 ip4:95.140.163.40 ip4:95.140.163.41 ip4:66.159.232.92 ip4:143.55.149.242 -all
TXT_dmarc.alahli.comv=DMARC1; p=reject; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:haseen@rua.dmarc.gov.sa; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com,mailto:haseen@ruf.dmarc.gov.sa; fo=1
CAAalahli.com—
DSalahli.com32557 8 2 b7a13df7adeea22335d77cbef40bb6a5b309ddbca05e107153d85ec3b6795ca0
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