Digital exposure report
render.com
Good shape, with a few gaps worth closing this quarter.
Scanned: 2026-11-19 02:59 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS render.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://render.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- render.com
- Website request
- GET https://render.com/
- Scan time
- 2026-11-19 02:59:36 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 | 29/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 25/30 | The site instructs browsers to block common attacks. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+7
- 2.LowPermissions-Policy · Hardening gap+2
- 3.LowCSP — protection from script injection · Hardening gap+3
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 include:_spf.google.com include:stspg-customer.com include:_spf.salesforce.com include:21532664.spf10.hubspotemail.net ~all
$ dig +short TXT render.com
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; sp=reject; rua=mailto:re+m3u79gyogz8@inbound.dmarcdigests.com; aspf=r; pct=100;
$ dig +short TXT _dmarc.render.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, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqcGfYDt7YrY/ZjGtbSSRFKl4Xo6p… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqQJHurXXMZFx4c+rXuzj3SyVtHLv4IJi… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDUflAksB7Vk5bcoSs4ypLARWXtSdPRhVreyWvh…
$ dig +short TXT google._domainkey.render.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.
1 aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com
$ dig +short MX render.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://render.com/ returned HTTP 200 (final URL: https://render.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://render.com/
$ curl -sIL https://render.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://render.com/
HTTP 301 Location: https://render.com/
$ curl -sI http://render.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: Google Trust Services, expiring 2027-02-15 (88 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: Google Trust Services Valid from: 2026-11-17 Valid until: 2027-02-15 Names: render.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect render.com:443 -servername render.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://render.com/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: 'unsafe-inline', 'unsafe-eval' — weakens XSS protection.
Content-Security-Policy: script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.osano.com https://*.posthog.com https://*.i.posthog.com https://assets.calendly.com https://scout-cdn.salesloft.com https://snap.licdn.com https://www.google.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://www.googletagmanager.com https://www.gstatic.com ; connect-src 'self' https://*.algolia.net https://*.algolianet.com https://*.google-analytics.com https://*.google.com https://*.googletagmanager.com https://*.doubleclick.net https://www.googleadservices.com https://*.hsforms.com https://*.inkeep.com https://*.linkedin.com https://*.osano.com https://*.posthog.com https://*.i.posthog.com https://*.segment.com https://*.segment.io https://api.unifyintent.com https://api.ashbyhq.com https://cdn.growthbook.io https://cdn.sanity.io https://hubspot-forms-static-embed.s3.amazonaws.com https://pagead2.googlesyndication.com https://scout.salesloft.com https://translate.googleapis.com ; worker-src 'self' blob: https://*.osano.com; report-uri https://render.report-uri.com/r/t/csp/reportOnly; report-to wizard;
$ curl -sIL https://render.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: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://render.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://render.com/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Passed · Severity: OK · 3/3Internal URLs don't leak to external sites.
Referrer-Policy: same-origin
Referrer-Policy: same-origin
$ curl -sIL https://render.com/ | grep -i "Referrer-Policy"
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://render.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://render.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 render.com: NODATA
$ dig +short DS render.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 render.com SOA delv render.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:security@render.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issuewild "digicert.com" | 0 issuewild "letsencrypt.org" | 0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 iodef "mailto:security@render.com" 0 issue "digicert.com" 0 issue "letsencrypt.org" 0 issue "pki.goog; cansignhttpexchanges=yes" 0 issuewild "digicert.com" 0 issuewild "letsencrypt.org" 0 issuewild "pki.goog; cansignhttpexchanges=yes"
$ dig +short CAA render.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.
4 NS servers.
ns-1514.awsdns-61.org ns-1554.awsdns-02.co.uk ns-319.awsdns-39.com ns-784.awsdns-34.net
$ dig +short NS render.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 rulesNo gaps observed
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline1 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 | render.com | 216.24.57.1 |
| AAAA | render.com | — |
| MX | render.com | 1 aspmx.l.google.com | 10 alt3.aspmx.l.google.com | 10 alt4.aspmx.l.google.com | 5 alt1.aspmx.l.google.com | 5 alt2.aspmx.l.google.com |
| NS | render.com | ns-1514.awsdns-61.org | ns-1554.awsdns-02.co.uk | ns-319.awsdns-39.com | ns-784.awsdns-34.net |
| TXT | render.com | ZOOM_verify_AsuKt-XqRkSw8mYuMFoYFg | abuseipdb-verification=G677hp0H | airtable-verification=2591011300e5c9e4108befaf7e2ffa85 | anthropic-domain-verification-vhtccq=XAZ7nZA5yxfg6kAXejLjScIi8 | apple-domain-verification=2SiUDx4ZB44s8aa0 | code-storage-from-the-pierre-computer-company-domain-verification-4amm9p=sUg4rXsHxs2xraMEUPwgTzJis | cursor-domain-verification-1ajrgc=GNsQ8c88zcgTNHWdWvXrqCfrd | docker-verification=db54706b-c36e-4a50-8b30-b0fe68975c22 | docusign=668955c8-af93-4ce7-8a11-3f3a99aae715 | figma-domain-verification=fc6fc399327090df07814449c332880a88d0e15885acdd268feb1a3fddb6866e-1729022495 | google-site-verification=0-CHkW0--yVLmElTIX6JmFsNAdNyc5nEmUvL6U_ueBs | google-site-verification=2e9iNtY9aOzK_vGEB_Z06i02d0yqofHM9DbPBdIEVDE | google-site-verification=63wwDRe4yVbAYEnvanOvHRTa6g6kvBdH0vtTH-qXKBc | google-site-verification=wiJhYPu0wC4xBtH9raQpw0vqogWraVNofi6IHua3bvI | h1-domain-verification=fDPNXYVEWfhsiszrMwkE3wUoY6bk3csjosChGs1XYPSxgX12 | linear-domain-verification=ui35imxwqum9 | loom-site-verification=1e62eab7a7834a5d8a0a63b0edf90bcc | lovable_verification=cY5I1tAVvVwfYDGWvt00 | mixpanel-domain-verify=9ecbed68-d140-4e16-84cc-2b9ea12b7489 | notion-domain-verification=f6OTVMpeCQLWvriDibyQYtYqfknvJRKq163jZ1mT14l | notion-domain-verification=pi0dWflV8mlqndksuaWK6FoK8EIvd69pSJxxoYPEA7w | openai-domain-verification=dv-ICfxppvTyKhidQfuWGFvtEWD | plausible-sso-verification=62c162a8-dcc9-48b6-a906-d54012806ac1 | rippling-domain-verification=4d6d8db14853f4d4 | segment-site-verification=RkruwaX8caJkSeaAXweAYwga5BuLLlsT | status-page-domain-verification=fncnjxcjvxfj | stripe-verification=FE010F4FFA52E850595780CC65A85C169A5865DF40C2299DFF57F2B1F7278494 | v=spf1 include:_spf.google.com include:stspg-customer.com include:_spf.salesforce.com include:21532664.spf10.hubspotemail.net ~all | zapier-domain-verification-challenge=9eed40a2-6f47-437d-9633-6f74429a927a |
| TXT | _dmarc.render.com | v=DMARC1; p=reject; sp=reject; rua=mailto:re+m3u79gyogz8@inbound.dmarcdigests.com; aspf=r; pct=100; |
| CAA | render.com | 0 iodef "mailto:security@render.com" | 0 issue "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issuewild "digicert.com" | 0 issuewild "letsencrypt.org" | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| DS | render.com | — |