Digital exposure report
remote.com
Low exposure. The domain is well protected in most areas checked.
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 remote.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://remote.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- remote.com
- Website request
- GET https://remote.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 | 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 | 27/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.LowCSP — protection from script injection · Hardening gap+3
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. 4 of the 10 allowed DNS lookups.
v=spf1 include:_spf.google.com include:mailgun.org include:mail.zendesk.com include:7405301.spf03.hubspotemail.net -all
$ dig +short TXT remote.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; pct=100; fo=1; ri=3600; rua=mailto:f09f101f@dmarc.mailgun.org,mailto:b5564746@inbox.ondmarc.com,mailto:re+b869b9da0e8f@inbound.dmarcdigests.com; ruf=mailto:f09f101f@dmarc.mailgun.org,mailto:b5564746@inbox.ondmarc.com;
$ dig +short TXT _dmarc.remote.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. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAk2wt7XLSWllfsB7lIubckSSUk09B…
$ dig +short TXT google._domainkey.remote.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 remote.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://remote.com/ returned HTTP 200 (final URL: https://remote.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://remote.com/
$ curl -sIL https://remote.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 308 → https://remote.com/
HTTP 308 Location: https://remote.com/
$ curl -sI http://remote.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-20 (152 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-10-05 Valid until: 2027-04-20 Names: remote-website.remote.com, remote.com, website.eu-west-1.remote.com Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect remote.com:443 -servername remote.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=63072000 (730 days), includeSubDomains, preload. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
$ curl -sIL https://remote.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: no script-src/default-src — weakens XSS protection.
Content-Security-Policy: frame-ancestors 'self' https://app.contentstack.com https://eu-app.contentstack.com https://*.contentstack.com; object-src 'none'; base-uri 'self'
$ curl -sIL https://remote.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 frame-ancestors 'self' https://app.contentstack.com https://eu-app.contentstack.com https://*.contentstack.com
X-Frame-Options: SAMEORIGIN CSP frame-ancestors: 'self' https://app.contentstack.com https://eu-app.contentstack.com https://*.contentstack.com
$ curl -sIL https://remote.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://remote.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://remote.com/ | grep -i "Referrer-Policy"
Permissions-Policy
Passed · Severity: OK · 2/2The site restricts access to sensitive browser features.
Permissions-Policy: accelerometer=(), camera=(), microphone=(), geolocation=(), usb=(), gyroscope=(), magnetometer=(), ambient-light-sensor=()
Permissions-Policy: accelerometer=(), camera=(), microphone=(), geolocation=(), usb=(), gyroscope=(), magnetometer=(), ambient-light-sensor=()
$ curl -sIL https://remote.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://remote.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 remote.com: NODATA
$ dig +short DS remote.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 remote.com SOA delv remote.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:sre-team@remote.com" | 0 issue "amazontrust.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issuewild "amazontrust.com" | 0 issuewild "godaddy.com" | 0 issuewild "letsencrypt.org"
0 iodef "mailto:sre-team@remote.com" 0 issue "amazontrust.com" 0 issue "godaddy.com" 0 issue "letsencrypt.org" 0 issue "pki.goog" 0 issuewild "amazontrust.com" 0 issuewild "godaddy.com" 0 issuewild "letsencrypt.org"
$ dig +short CAA remote.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-1195.awsdns-21.org ns-120.awsdns-15.com ns-1790.awsdns-31.co.uk ns-522.awsdns-01.net
$ dig +short NS remote.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 | remote.com | 162.251.205.15 |
| AAAA | remote.com | — |
| MX | remote.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 | remote.com | ns-1195.awsdns-21.org | ns-120.awsdns-15.com | ns-1790.awsdns-31.co.uk | ns-522.awsdns-01.net |
| TXT | remote.com | 1password-site-verification=D56757PPAJDCXLUGY5IOC6WAQA | MS=ms60374780 | adobe-idp-site-verification=9054f7913d2bdf825ddd903b0bc9a4dea75e6dcb831ef1950e01565e81423162 | ahrefs-site-verification_fe8e8271b2a422e228439474c0f73c88cbbf9af94934b1b6bca49fa0cf709aa9 | anthropic-domain-verification-bf5sz2=8IWlDcVOD06xND3Ni1I3G9fIr | apple-domain-verification=fSVgSYgDKjABjQKw | cursor-domain-verification-351h4k=RcScPa53Y9aVulRrGZTwuZCrD | docusign=e5e0606b-24c0-4ba1-881a-f3cf14eddb95 | drift-domain-verification=011b81edfb2201ef099299cd63d4831838c315cb2f431c47eccc62bfda6d3357 | ethiack-verification=4e156534ccdf262d5d2a4651abcb994593bd2487f4bc8fb34ea91fa3b9271f79d4d03fa64b4ac96477989cfdb842bc7aecce8a2b4b759bcfb7b9a19c4f6a4512 | facebook-domain-verification=v3i69hyy3cm5o6q3eyy8lruvzmp0ey | google-site-verification=9_pVJ4G8ZYUzSNaq6oR9UaLEiKRXfY8iwEBU6-kx3n4 | google-site-verification=E7fxWOTsoXjI3bd1-P-xb86wr5W5irFS9TDUK86e9Bc | google-site-verification=FC6TbSChB2hHjOsq-Ox1rJuOw3RygWipBCOxp7cY4gk | google-site-verification=eFCJtxKaK3rmWdFxolqLt7OIOnr-i4i1mM3KDDZU5kk | google-site-verification=lRmuM80amzxKXer8RatuzAdE2IcP4fMFaTxFJmrQIaU | google-site-verification=o6MGM2VdPflTDsTkUsEQvP3QwiMVfa4RTKBrv825bd8 | h1-domain-verification=KVSaj3nHNpJBeawd2YM5MwcrJfENtjoFW2o8UT5xZWaFEk9p | hubspot-domain-verification=NGIyNmFlODYtZjNiMi00MmE0LWFhYmYtMzJkZjM2YzE4YTA0 | kota-domain-verification-tsyj47=GQCRhx4ZaLkVb3MoTpWISJJ43 | linear-domain-verification=q8gcsxftuw5j | lovable_verification=workspace_01k486dvtef1mrsy64e7mmnxtf | miro-verification=fae08428b5f8bf93de251de2a18552b4fdaf53d7 | mixpanel-domain-verify=94dc2fe2-8127-4bed-943f-44d78c305ac4 | notion-domain-verification=9Jux8F5Pe5eIQncmBFdzi2GCuNn0WsXq4Vnoa9b1A3D | nyfbxw311vzkcd3fg1dgss5zwkdbfpk9 | openai-domain-verification=dv-ANLxeNIwiv33kwO29jAXVGge | parallels-domain-verification=fe47c3aadfed4aac992f01b294eeda9ccd27a7d9bd824995979d78e292e8ee0e | protonmail-verification=73a48cc3995d754f68be5912c2c34fb21cb4942d | remote-domain-verification=2df9bc51-642d-4b4c-adfd-70e1e3e0a853 | slack-domain-verification=8dNOTXHCTl7LogHdudOA6C6JdjJ8BGhtXs6k6N5T | stripe-verification=370be9902e28e1a646dfeae7cc95156c29bd6e47641b5a286f480bc1e323fe8d | v=spf1 include:_spf.google.com include:mailgun.org include:mail.zendesk.com include:7405301.spf03.hubspotemail.net -all |
| TXT | _dmarc.remote.com | v=DMARC1; p=reject; pct=100; fo=1; ri=3600; rua=mailto:f09f101f@dmarc.mailgun.org,mailto:b5564746@inbox.ondmarc.com,mailto:re+b869b9da0e8f@inbound.dmarcdigests.com; ruf=mailto:f09f101f@dmarc.mailgun.org,mailto:b5564746@inbox.ondmarc.com; |
| CAA | remote.com | 0 iodef "mailto:sre-team@remote.com" | 0 issue "amazontrust.com" | 0 issue "godaddy.com" | 0 issue "letsencrypt.org" | 0 issue "pki.goog" | 0 issuewild "amazontrust.com" | 0 issuewild "godaddy.com" | 0 issuewild "letsencrypt.org" |
| DS | remote.com | — |