videoly.net security report

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

9risk

Low

Minor observations only.

0Critical

0High

0Medium

11Low

1Info

Collected 1 hour ago94.5sfrom cache

Headers—

unavailable

Domain—

unavailable

Certificate Transparency48
DNS resolution36
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs44
Registration
DNS posture2
Email authentication2
Certificate
Security headers
Archived URLs
Analysis12

noteFound 48 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 19 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.
noteRegistration 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.
note3 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

gitlab.videoly.net 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: gitlab.videoly.net
test.videoly.net 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: test.videoly.net
redis-test.videoly.net 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: redis-test.videoly.net
my-client-dev.videoly.net 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: my-client-dev.videoly.net
pgbouncer-test.videoly.net 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: pgbouncer-test.videoly.net
shop99.test-dapi.videoly.net 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: shop99.test-dapi.videoly.net
v4b-backend-stage.videoly.net 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: v4b-backend-stage.videoly.net
v4b-uploader-stage.videoly.net 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: v4b-uploader-stage.videoly.net
shop100077.test-dapi.videoly.net 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: shop100077.test-dapi.videoly.net
load-test-pgbouncer-v4r.videoly.net 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: load-test-pgbouncer-v4r.videoly.net
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: videoly.net
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: videoly.net

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
✓SPFends in -all
v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:amazonses.com -all
✓DMARCp=reject
v=DMARC1; p=reject; pct=100; rua=mailto:re+0b4fc6213a3a@inbound.dmarcdigests.com; sp=reject; aspf=r; adkim=r;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "amazon.com" · 0 issue "comodoca.com" · 0 issue "digicert.com; cansignhttpexchanges=yes" · 0 issue "letsencrypt.org" · 0 issue "pki.goog; cansignhttpexchanges=yes" · 0 issue "ssl.com" · 0 issuewild "comodoca.com" · 0 issuewild "digicert.com; cansignhttpexchanges=yes" · 0 issuewild "letsencrypt.org" · 0 issuewild "pki.goog; cansignhttpexchanges=yes" · 0 issuewild "ssl.com"
✓IPv6 (AAAA)
✓2 nameservers
gail.ns.cloudflare.com norm.ns.cloudflare.com

Address	Ports	Edge	Network
104.26.15.178 videoly.net +4	80443205220532082208320862087+4	Cloudflare~	—
172.67.74.183 videoly.net +3	80443205220822083208620872096+3	Cloudflare~	—
104.26.14.178 videoly.net +3	80443208220832086208720958080+2	Cloudflare~	—
44.207.89.240 v4b-uploader-stage.videoly.net +1	80443	direct	—
3.33.148.61 shop99.test-dapi.videoly.net +4	80443	direct	—
13.248.144.105 shop99.test-dapi.videoly.net +4	80443	direct	—
13.248.241.119 shop99.test-dapi.videoly.net +4	80443	direct	—
35.71.131.46 shop99.test-dapi.videoly.net +4	80443	direct	—
75.126.104.226 redis-test.videoly.net +9	80	direct	—
3.92.123.174 test.videoly.net	none known	direct	—
40.112.61.235 dev1.videoly.net	none known	direct	—
44.196.96.63 dev3.videoly.net	none known	direct	—

Archived URLs

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

videoly.net security report

Low

Findings

Email authentication

DNS

Hosts

Hostnames