Digital exposure report
ree.auto
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-19 02:59 UTC
Full coverage: every applicable check was assessed.
What to do first
- 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.ree.auto
- 2.
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://ree.auto/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- ree.auto
- Website request
- GET https://ree.auto/
- Scan time
- 2026-11-19 02:59:47 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 | 18/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 21/30 | Some browser protections are missing. |
| DNS infrastructure | 10/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDMARC — anti-spoofing policy · Hardening gap+11
- 2.MediumCSP — protection from script injection · Hardening gap+8
- 3.LowCAA — who may issue certificates · Hardening gap+5
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 4 of 10 DNS lookups.
v=spf1 a mx include:_spf.elasticemail.com ip4:62.128.35.175 ip4:54.227.64.76 ip4:3.95.142.181 ip4:3.95.118.12 ip4:3.93.155.149 ip4:3.81.182.154 include:spf.protection.outlook.com ~all
$ dig +short TXT ree.auto
DMARC — anti-spoofing policy
Needs attention · Severity: Medium · Hardening gap · 4/15DMARC is in monitoring mode only — forged email still reaches recipients.
Policy p=none. p=none collects reports but does not protect. No rua — no reports on spoofing attempts are received.
v=DMARC1; p=none;
$ dig +short TXT _dmarc.ree.auto
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.ree.auto. TXT "v=DMARC1; p=none; rua=mailto:dmarc@ree.auto; 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.
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: selector1. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDDIBG3Jbv4qTSnIrqTC4f0DU4PLLs6J93P…
$ dig +short TXT selector1._domainkey.ree.auto
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.
0 ree-auto.mail.protection.outlook.com
$ dig +short MX ree.auto
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://ree.auto/ returned HTTP 200 (final URL: https://ree.auto/). Client-side certificate validation passed.
HTTP 200 Final URL: https://ree.auto/
$ curl -sIL https://ree.auto/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://ree.auto/
HTTP 301 Location: https://ree.auto/
$ curl -sI http://ree.auto/ | 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. No matching certificate details were available from CT logs; run the verify command to see the served certificate's dates.
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 ree.auto:443 -servername ree.auto 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=63072000 (730 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000
$ curl -sIL https://ree.auto/ | 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://ree.auto/ | 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
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://ree.auto/ | grep -i "X-Frame-Options"
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://ree.auto/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: strict-origin-when-cross-origin
Referrer-Policy: strict-origin-when-cross-origin
$ curl -sIL https://ree.auto/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: accelerometer=(), autoplay=(), camera=(), cross-origin-isolated=(), display-capture=(self), encrypted-media=(), fullscreen=*, geolocation=(self), gyroscope=(),
Permissions-Policy: accelerometer=(), autoplay=(), camera=(), cross-origin-isolated=(), display-capture=(self), encrypted-media=(), fullscreen=*, geolocation=(self), gyroscope=(), keyboard-map=(), magnetometer=(), microphone=(), midi=(), payment=*, picture-in-picture=*, publickey-credentials-get=(), screen-wake-lock=(), sync-xhr=*, usb=(), xr-spatial-tracking=(), gamepad=(), serial=()
$ curl -sIL https://ree.auto/ | grep -i "Permissions-Policy"
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://ree.auto/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec ree.auto | grep -E "flags:.* ad"
CAA — who may issue certificates
Needs attention · Severity: Low · Hardening gap · 0/5Any 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.
(no CAA records found)
$ dig +short CAA ree.auto
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
ree.auto. CAA 0 issue "letsencrypt.org" ree.auto. CAA 0 iodef "mailto:security@ree.auto"
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.
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
blair.ns.cloudflare.com hugh.ns.cloudflare.com
$ dig +short NS ree.auto
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.01 observed gaps
- NIS2 / vendor due diligence2 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 | ree.auto | 159.65.88.50 |
| AAAA | ree.auto | — |
| MX | ree.auto | 0 ree-auto.mail.protection.outlook.com |
| NS | ree.auto | blair.ns.cloudflare.com | hugh.ns.cloudflare.com |
| TXT | ree.auto | Account Engagement emails pass SPF automatically, but we recommend setting it up as a best practice. | atlassian-domain-verification=j57XMZigTd4Dga87GfVokfdiueXUaaBXrFy/Sf7TD3cVLM5JI3/vGga606VovIJB | openai-domain-verification=dv-cqH2dvHS0Zqpm14JRQqIzqv5 | sending_domain1062552=d6c5aed1f7849591b20429bb6c1dd9c7e2f65b89afe026028811fcca3fa0e057 | v=spf1 a mx include:_spf.elasticemail.com ip4:62.128.35.175 ip4:54.227.64.76 ip4:3.95.142.181 ip4:3.95.118.12 ip4:3.93.155.149 ip4:3.81.182.154 include:spf.protection.outlook.com ~all |
| TXT | _dmarc.ree.auto | v=DMARC1; p=none; |
| CAA | ree.auto | — |
| DS | ree.auto | — |