zencoder.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

9risk

Low

Minor observations only.

0Critical

0High

0Medium

13Low

2Info

Collected 8 hours ago2.1sfrom cache

Headers—

unavailable

Certificate Transparency24
DNS resolution33
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs15
Registration
DNS posture4
Email authentication2
Certificate
Security headers
Archived URLs
Analysis15

noteFound 24 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 33 addresses; enriching the first 12.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteSecurity headers did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.

qa.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: qa.zencoder.com
stage.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: stage.zencoder.com
qa-api.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: qa-api.zencoder.com
staging.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: staging.zencoder.com
www-stage.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www-stage.zencoder.com
www.stage.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.stage.zencoder.com
blog-stage.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: blog-stage.zencoder.com
qa-api-alb.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: qa-api-alb.zencoder.com
www.www-stage.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.www-stage.zencoder.com
www.blog-stage.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.blog-stage.zencoder.com
internal.api.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: internal.api.zencoder.com
www.internal.api.zencoder.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.internal.api.zencoder.com
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: zencoder.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: zencoder.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: zencoder.com

✓Receives mail via 7 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com aspmx.l.google.com aspmx2.googlemail.com+3
✓SPFends in -all
v=spf1 include:_spf.google.com include:servers.mcsv.net include:spf.mtasv.net include:spf.mandrillapp.com -all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:f578d1f03d67304@rep.dmarcanalyzer.com; ruf=mailto:f578d1f03d67304@for.dmarcanalyzer.com; fo=1;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1412.awsdns-48.org ns-1796.awsdns-32.co.uk ns-753.awsdns-30.net ns-76.awsdns-09.com

✓Registered with Gandi SAS25.0 years old
zencoder.com
✓Registration expiry354 days
2027-08-27
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1412.awsdns-48.org ns-1796.awsdns-32.co.uk ns-753.awsdns-30.net ns-76.awsdns-09.com

Address	Ports	Edge	Network
13.249.231.87 zencoder.com +2	80443	direct	—
13.249.231.76 zencoder.com +2	80443	direct	—
13.249.231.99 zencoder.com +2	80443	direct	—
13.249.231.120 zencoder.com +2	80443	direct	—
52.86.84.243 staging.zencoder.com +2	80443	direct	—
18.155.68.7 www.zencoder.com +14	80443	direct	—
98.90.178.176 staging.zencoder.com +2	443	direct	—
44.221.108.234 staging.zencoder.com +2	443	direct	—
18.155.68.64 www.zencoder.com +1	80	direct	—
52.200.48.20 stage.zencoder.com	none known	direct	—
18.210.3.244 staging.zencoder.com	none known	direct	—
166.78.234.12 www-stage.zencoder.com	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

zencoder.com security report

Low

Findings

Email authentication

DNS

Registration

Hosts

Hostnames