Digital exposure report
waveapps.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.
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://waveapps.com/ | grep -i "Content-Security-Policy"
- 2.
List the servers allowed to send your email
Without this list, it is easier for others to send email that looks like it came from you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT waveapps.com
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- waveapps.com
- Website request
- GET https://waveapps.com/ → https://www.waveapps.com/
- Scan time
- 2026-11-19 02:59:37 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 | 22/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 | 11/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 10/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumSPF — who may send mail for the domain · Hardening gap+6
- 2.MediumClickjacking protection · Hardening gap+5
- 3.MediumCSP — protection from script injection · Hardening gap+8
- 4.LowCAA — who may issue certificates · Hardening gap+5
- 5.LowReferrer-Policy · Hardening gap+3
- 6.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Needs attention · Severity: Medium · Hardening gap · 4/10The SPF record is neutral and does not block unauthorized senders.
?all (neutral) does not tell the receiving server to reject or flag mail from servers not on the list.
v=spf1 include:_spf.google.com include:spf.protection.outlook.com include:spf.mtasv.net include:4645450.spf02.hubspotemail.net include:mail.zendesk.com include:email.chargebee.com include:mailgun.org ?all
$ dig +short TXT waveapps.com
- Map every service that sends mail in the domain's name (Google Workspace / Microsoft 365, newsletter tool, CRM).
- Publish exactly one TXT record at the domain root starting with v=spf1.
- Start with ~all, and move to -all once DMARC reports confirm all legitimate senders are covered.
waveapps.com. TXT "v=spf1 include:_spf.google.com ~all"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. An incorrect record can block legitimate mail — add every sender before tightening.
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; sp=quarantine; rua=mailto:re+d7b390d63c21@inbound.dmarcdigests.com; adkim=r; aspf=r; rf=afrf; pct=100
$ dig +short TXT _dmarc.waveapps.com
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, selector1, selector2, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAut1kBBrVzh/ovpcPaCr10G0ksr2F… selector1._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDBrGkzVzKVxK546HuhXZzTdeBxkxEFGSNU… selector2._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDXDKbfXU0UZ7MCbFB+YkQASjMhGFsEQkAy… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA5CPjIwVH/jfTIoGFFFpyMoeeXZqrM4hm… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDpDCE+FicPuc28f0mppTrjpIHMXo2RQw3wFWU/…
$ dig +short TXT google._domainkey.waveapps.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 20 alt2.aspmx.l.google.com 30 aspmx2.googlemail.com 30 aspmx3.googlemail.com
$ dig +short MX waveapps.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://waveapps.com/ returned HTTP 200 (final URL: https://www.waveapps.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.waveapps.com/
$ curl -sIL https://waveapps.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://waveapps.com/
HTTP 301 Location: https://waveapps.com/
$ curl -sI http://waveapps.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: Amazon Trust Services, expiring 2027-04-08 (140 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: Amazon Trust Services Valid from: 2026-09-22 Valid until: 2027-04-08 Names: *.waveapps.com, waveapps.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect waveapps.com:443 -servername waveapps.com 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://waveapps.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://waveapps.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
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://waveapps.com/ | 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://waveapps.com/ | 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://waveapps.com/ | 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://waveapps.com/ | 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://waveapps.com/ | 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 waveapps.com | 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 waveapps.com
- Identify which certificate authority issued your current certificate (see the certificate check).
- Publish CAA for that authority only, and add iodef to receive alerts.
waveapps.com. CAA 0 issue "letsencrypt.org" waveapps.com. CAA 0 iodef "mailto:security@waveapps.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.
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.
rick.ns.cloudflare.com athena.ns.cloudflare.com
$ dig +short NS waveapps.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.02 observed gaps
- NIS2 / vendor due diligence2 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
| A | waveapps.com | 198.202.211.1 |
| AAAA | waveapps.com | 2620:cb:2000::1 |
| MX | waveapps.com | 10 aspmx.l.google.com | 20 alt1.aspmx.l.google.com | 20 alt2.aspmx.l.google.com | 30 aspmx2.googlemail.com | 30 aspmx3.googlemail.com |
| NS | waveapps.com | rick.ns.cloudflare.com | athena.ns.cloudflare.com |
| TXT | waveapps.com | MS=ms46765856 | proxy-ssl.webflow.com | onx=1a3c4996-115a-4ffb-9a4e-db05a36ebe68 | onx=5f9d8640-4d29-49ff-ad6a-bb9c109d7b8e | onx=7e4d9692-11d2-43c2-9376-5da03a258279 | onx=c69a41ef-124d-4c33-860e-cc17e5795563 | cloudpiercer-verification=9c702cbdc46c7b2edd7ded8945b342bb | knowbe4-site-verification=a29eb46b67b94c52ee4e2e8d9d71803d | miro-verification=533f19bc74ae3753979bd0562f02ee373d56cb36 | segment-site-verification=61ofunXVpePiC4CZc8GB99WgOYqxCWoy | google-site-verification=H171sqL7OU6vpLtiW4JYBmMiNHeUf2Z1GvmkYSgERKM | google-site-verification=NqEAyZ0h7gBpHhppNfWkNSfCDwN6Bh7q9xnerCFcH6Y | google-site-verification=eqB1N9QIXQSgRa1mdN80GlQ8MscjUciVO0dL4t_xd_4 | google-site-verification=q8xoLT2u1CwVf_Lm1H7j3PqeeSwdIYBZXHBCQX3OYfY | hubspot-domain-verification=NDEzM2FlMDUtNzVlNC00ZWU4LWJkN2YtNDIzNzhiNTEyNzgy | v=spf1 include:_spf.google.com include:spf.protection.outlook.com include:spf.mtasv.net include:4645450.spf02.hubspotemail.net include:mail.zendesk.com include:email.chargebee.com include:mailgun.org ?all |
| TXT | _dmarc.waveapps.com | v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:re+d7b390d63c21@inbound.dmarcdigests.com; adkim=r; aspf=r; rf=afrf; pct=100 |
| CAA | waveapps.com | — |
| DS | waveapps.com | 2371 13 2 1aad5d18dc7de8399e089739c834f55e33c8290144943cc8663fbdd7dfea8341 |