Digital exposure report
aidoc.com
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-20 07:34 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.aidoc.com
- 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://aidoc.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- aidoc.com
- Website request
- GET https://aidoc.com/ → https://www.aidoc.com/
- Scan time
- 2026-11-20 07:34:32 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 | 19/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 | 22/30 | Some browser protections are missing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDMARC — anti-spoofing policy · Hardening gap+10
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.MediumCSP — protection from script injection · Hardening gap+8
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. 7 of 10 DNS lookups.
v=spf1 include:_spf.google.com include:_spf.salesforce.com include:5748396.spf02.hubspotemail.net include:amazonses.com include:stspg-customer.com include:_spf.psm.knowbe4.com include:docebosaas.com ~all
$ dig +short TXT aidoc.com
DMARC — anti-spoofing policy
Needs attention · Severity: Medium · Hardening gap · 5/15DMARC is in monitoring mode only — forged email still reaches recipients.
Policy p=none. p=none collects reports but does not protect.
v=DMARC1; p=none; rua=mailto:dmarc-report@aidoc.com; ruf=mailto:dmarc-failure@aidoc.com; fo=0
$ dig +short TXT _dmarc.aidoc.com
- 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.aidoc.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@aidoc.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.
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, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC+6oXaD+PqRPBUVets8xyErbwPOd+fa++a… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs06b33SACJHpdxIoHLLDSDLd76yB5O7d… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDRnPiVLd3pUOmYKwPaLevrjtXKgJYUDgaW3Bbv…
$ dig +short TXT google._domainkey.aidoc.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
6 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
0 inbound-smtp.eu-west-1.amazonaws.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 2 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com
$ dig +short MX aidoc.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://aidoc.com/ returned HTTP 200 (final URL: https://www.aidoc.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.aidoc.com/
$ curl -sIL https://aidoc.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://aidoc.com/
HTTP 301 Location: https://aidoc.com/
$ curl -sI http://aidoc.com/ | 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: DigiCert, expiring 2027-03-06 (106 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: DigiCert Valid from: 2026-02-03 Valid until: 2027-03-06 Names: *.aidoc.com, aidoc.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect aidoc.com:443 -servername aidoc.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
$ curl -sIL https://aidoc.com/ | 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://aidoc.com/ | 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: DENY
X-Frame-Options: DENY
$ curl -sIL https://aidoc.com/ | 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://aidoc.com/ | 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://aidoc.com/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()
Permissions-Policy: geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()
$ curl -sIL https://aidoc.com/ | 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: WP Engine
$ curl -sIL https://aidoc.com/ | 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 aidoc.com: NODATA
$ dig +short DS aidoc.com
- 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 aidoc.com SOA delv aidoc.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.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 iodef "mailto:it@aidoc.com " | 0 issue "comodoca.com" | 0 issue "digicert.com; cansignhttpexchanges=yes" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issue "ssl.com" | 0 issuewild "comodoca.com" | 0 issuewild "digicert.com; cansignhttpexchanges=yes" | 0 issuewild "letsencrypt.org" | 0 issuewild "pki.goog; cansignhttpexchanges=yes" | 0 issuewild "ssl.com"
0 iodef "mailto:it@aidoc.com " 0 issue "comodoca.com" 0 issue "digicert.com; cansignhttpexchanges=yes" 0 issue "letsencrypt.org" 0 issue "pki.goog; cansignhttpexchanges=yes" 0 issue "ssl.com" 0 issuewild "comodoca.com" 0 issuewild "digicert.com; cansignhttpexchanges=yes" 0 issuewild "letsencrypt.org" 0 issuewild "pki.goog; cansignhttpexchanges=yes" 0 issuewild "ssl.com"
$ dig +short CAA aidoc.com
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.
dion.ns.cloudflare.com rafe.ns.cloudflare.com
$ dig +short NS aidoc.com
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 | aidoc.com | 104.21.7.25 | 172.67.135.167 |
| AAAA | aidoc.com | 2606:4700:3037::6815:719 | 2606:4700:3031::ac43:87a7 |
| MX | aidoc.com | 0 inbound-smtp.eu-west-1.amazonaws.com | 10 alt3.aspmx.l.google.com | 10 alt4.aspmx.l.google.com | 2 aspmx.l.google.com | 5 alt1.aspmx.l.google.com | 5 alt2.aspmx.l.google.com |
| NS | aidoc.com | dion.ns.cloudflare.com | rafe.ns.cloudflare.com |
| TXT | aidoc.com | 00DVe000005MIQ1=1TBVe0000000EPZ | 49AB294DCA | MS=ms42154688 | NW56G3L795S2G5P7L574OY67YK5YV11FFNKWZGLG | ZOOM_verify_E85buIVHISk40RUcOuwHpC | _sdlgc83xbtqr1mc1d2sbgr3mxknj51b | anthropic-domain-verification-gawb9s=nQxa22t9qm3UfJUPaaSnbhYmu | apple-domain-verification=FHyHN8KlQLly3D2x | atlassian-domain-verification=eBi4NFGjUDemmATjW3E5sEngyVeexYfgtz3D4KSMQahQqfnxU5XSWy5Tpjaa3Ro/ | atlassian-sending-domain-verification=9c67af3e-ba9f-41c1-b354-e2416194e6b3 | cursor-domain-verification-4mhz1e=K8R2GSYSdQPoQnvJpuOcOfFMR | google-site-verification=UuiiUj31KVzrUjVbDGCkONRhZAHn9cU9intPJEAea8Y | hubspot-domain-verification=NjUyN2FmZDgtMGQzOS00MWJlLWEwYWEtNjAyNWI4ZDUzM2Q3 | pendo-domain-verification=gm70qtsw_SwukRPR-FE0Y39Uvck | r1v08skkt9r8m1t99q4tlz0ghc32m6rh | status-page-domain-verification=r0jdszt6qmqm | v=spf1 include:_spf.google.com include:_spf.salesforce.com include:5748396.spf02.hubspotemail.net include:amazonses.com include:stspg-customer.com include:_spf.psm.knowbe4.com include:docebosaas.com ~all |
| TXT | _dmarc.aidoc.com | v=DMARC1; p=none; rua=mailto:dmarc-report@aidoc.com; ruf=mailto:dmarc-failure@aidoc.com; fo=0 |
| CAA | aidoc.com | 0 iodef "mailto:it@aidoc.com " | 0 issue "comodoca.com" | 0 issue "digicert.com; cansignhttpexchanges=yes" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issue "ssl.com" | 0 issuewild "comodoca.com" | 0 issuewild "digicert.com; cansignhttpexchanges=yes" | 0 issuewild "letsencrypt.org" | 0 issuewild "pki.goog; cansignhttpexchanges=yes" | 0 issuewild "ssl.com" |
| DS | aidoc.com | — |