Digital exposure report
vultr.com
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-19 02:55 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://vultr.com/ | grep -i "Strict-Transport-Security"
- 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://vultr.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- vultr.com
- Website request
- GET https://vultr.com/ → https://www.vultr.com/
- Scan time
- 2026-11-19 02:55:38 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 | 30/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 | 14/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 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 · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 6 of the 10 allowed DNS lookups.
v=spf1 ip4:108.61.13.174 ip4:107.191.35.128/29 ip4:208.167.225.32/28 ip4:208.167.225.253 ip4:66.42.112.23 ip4:108.61.150.28 ip4:64.237.34.251 ip4:192.254.117.0/24 include:_spf2.vultr.com include:_spf3.vultr.com include:_spf.google.com include:_spf4.vultr.com include:mg-spf.greenhouse.io include:usb._netblocks.mimecast.com -all
$ dig +short TXT vultr.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; rua=mailto:noreply@vultr.com; ruf=mailto:noreply@vultr.com; pct=100; sp=reject; fo=1; ri=3600;
$ dig +short TXT _dmarc.vultr.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=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwXZQDvHGpS6vMlrprpRh7WF9kZIM… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArrD2RANgOSplt0K19St5vEhQWF9VsoUP… s2._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw+RmWuhSZnD44Kexqf00ogL0BjXbUOKA…
$ dig +short TXT google._domainkey.vultr.com
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
7 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
15 usb-smtp-inbound-2.mimecast.com 15 usb-smtp-inbound-1.mimecast.com 5 alt3.aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt4.aspmx.l.google.com 5 aspmx.l.google.com
$ dig +short MX vultr.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://vultr.com/ returned HTTP 403 (final URL: https://www.vultr.com/). Client-side certificate validation passed.
HTTP 403 Final URL: https://www.vultr.com/
$ curl -sIL https://vultr.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://www.vultr.com/
HTTP 301 Location: https://www.vultr.com/
$ curl -sI http://vultr.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: Sectigo, expiring 2027-05-06 (168 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: Sectigo Valid from: 2026-10-20 Valid until: 2027-05-06 Names: *.vultr.com, vultr.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect vultr.com:443 -servername vultr.com 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Failed · Severity: High · Hardening gap · 0/8Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.
No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.
Strict-Transport-Security: (missing)
$ curl -sIL https://vultr.com/ | grep -i "Strict-Transport-Security"
- Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
- Gradually raise it to 31536000 (one year) and add includeSubDomains.
- Consider preload only once the policy is stable — removal from the preload list is slow.
/* Strict-Transport-Security: max-age=31536000; includeSubDomains
Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.
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://vultr.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://vultr.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://vultr.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://vultr.com/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credential
Permissions-Policy: accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
$ curl -sIL https://vultr.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: (missing)
$ curl -sIL https://vultr.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 vultr.com: NODATA
$ dig +short DS vultr.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 vultr.com SOA delv vultr.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 issue "pki.goog" | 0 issue "ssl.com" | 0 issue "digicert.com" | 0 issue "comodoca.com" | 0 issue "globalsign.com"
0 issue "pki.goog" 0 issue "ssl.com" 0 issue "digicert.com" 0 issue "comodoca.com" 0 issue "globalsign.com"
$ dig +short CAA vultr.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.
ns1.vultr.com ns2.vultr.com
$ dig +short NS vultr.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.02 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 | vultr.com | 108.61.13.174 |
| AAAA | vultr.com | 2001:19f0:200:4d1e::5663 |
| MX | vultr.com | 15 usb-smtp-inbound-2.mimecast.com | 15 usb-smtp-inbound-1.mimecast.com | 5 alt3.aspmx.l.google.com | 5 alt2.aspmx.l.google.com | 5 alt1.aspmx.l.google.com | 5 alt4.aspmx.l.google.com | 5 aspmx.l.google.com |
| NS | vultr.com | ns1.vultr.com | ns2.vultr.com |
| TXT | vultr.com | v=spf1 ip4:108.61.13.174 ip4:107.191.35.128/29 ip4:208.167.225.32/28 ip4:208.167.225.253 ip4:66.42.112.23 ip4:108.61.150.28 ip4:64.237.34.251 ip4:192.254.117.0/24 include:_spf2.vultr.com include:_spf3.vultr.com include:_spf.google.com include:_spf4.vultr.com include:mg-spf.greenhouse.io include:usb._netblocks.mimecast.com -all | MS=ms86697215 | google-site-verification=Ryn0Aj4JR2jZqIdcPW7kSJqXfs5SbapmIxaxh9lWU_c | google-site-verification=WDIvV4I3oxoMb_YaS3aeHtjxFfbxCcSxqSLQF-1pa70 | google-site-verification=GqCSqlqKVppVZRlgvbH_hTGZWJVl7e977tVzU73uVs4 | ZOOM_verify_9ywASGj6PuIA9N2HYZVRrf | apple-domain-verification=CxqfTABZC1giQ19T | atlassian-domain-verification=wVgYGZnIYvvraibwX49cBONcBWHWYL81LA1uWodeM7IdQxwSyYazmIIO/3CUsXhA | MS=ms10923579 | loom-site-verification=eb0c18d0804e4dd084b81a3cf24c3183 | pendo-domain-verification=d872d923-c971-401c-bd68-243658c2db46 | google-site-verification=GbzFKZkq8DWEt5x7PmoA3Pxagm8NKygpLG_oZ1e78IU | docusign=633cc0ac-debd-4242-afb1-7ae870e91ead | canva-site-verification=w0pZUeOvw9MJlURorbrEdQ | adobe-idp-site-verification=fa9185e0e115144ccda8e30655525daeab50d465acd43b25c476a64696924958 | bw=Z55D5lLY20P85qTAKc4S2fUnp00a0VWh7SEmMaTZrIza | google-site-verification=9sdWdviwsHEWCTw9ZWhhQsmIp2_DOgrGSkxam4iFMYw | miro-verification=88cf1e2f34c6e21df44698fe13d9d91c763458dd | docker-verification=573667a1-7809-4032-b99d-a1215beb56cf | fastly-domain-delegation-jbqvn47vwsvcchugr7hv-883667-2025-02-19 | airtable-verification=7709b3d95fefc3b3dce33855b0c92ec9 | dell-technologies-domain-verification=vultr.com_87458624-b58a-4e9d-890c-bebf83011050_1754052576 | anthropic-domain-verification-pf019j=opDZfUiEhITcXFkpEjXP3tHjL | smartsheet-site-validation=fy-05zGqWk1llWCnnVtnC-IeF9317Gj5 | _chk9ed1t98n92uc1gmbgsfc6s0kvg8q | figma-domain-verification=7db35b3e83fe2fc964fa250cf0ebd129a9966c71a6627aa3ef65617a14a3f17b-1789142174 |
| TXT | _dmarc.vultr.com | v=DMARC1; p=reject; rua=mailto:noreply@vultr.com; ruf=mailto:noreply@vultr.com; pct=100; sp=reject; fo=1; ri=3600; |
| CAA | vultr.com | 0 issue "pki.goog" | 0 issue "ssl.com" | 0 issue "digicert.com" | 0 issue "comodoca.com" | 0 issue "globalsign.com" |
| DS | vultr.com | — |