autodoc.dk security report

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

32risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

0Medium

21Low

2Info

Collected 17 hours ago4.8sfrom cache

Certificate Transparency474
DNS resolution42
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs21
Registration
DNS posture2
Email authentication2
Certificate
Security headers6
Archived URLs
Analysis24

noteFound 474 hostnames; resolving the first 400.
noteFound 400 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.
noteNo registration data: RDAP has no record at this level.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://autodoc.dk/
dev-php80.autodoc.dk 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: dev-php80.autodoc.dk
dev-sales.autodoc.dk 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: dev-sales.autodoc.dk
dev-ci-fix.autodoc.dk 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: dev-ci-fix.autodoc.dk
dev-jquery.autodoc.dk 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: dev-jquery.autodoc.dk
dev-paypal.autodoc.dk 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: dev-paypal.autodoc.dk
dev-pb4967.autodoc.dk 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: dev-pb4967.autodoc.dk
dev-pb5691.autodoc.dk 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: dev-pb5691.autodoc.dk
dev-newcart.autodoc.dk 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: dev-newcart.autodoc.dk
dev-pbb3974.autodoc.dk 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: dev-pbb3974.autodoc.dk
dev-prf-new.autodoc.dk 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: dev-prf-new.autodoc.dk
dev-seo3484.autodoc.dk 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: dev-seo3484.autodoc.dk
dev-seo3488.autodoc.dk 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: dev-seo3488.autodoc.dk
dev-seo3674.autodoc.dk 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: dev-seo3674.autodoc.dk
dev-seo3872.autodoc.dk 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: dev-seo3872.autodoc.dk
dev-seo4000.autodoc.dk 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: dev-seo4000.autodoc.dk
dev-seo4137.autodoc.dk 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: dev-seo4137.autodoc.dk
dev-seo4198.autodoc.dk 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: dev-seo4198.autodoc.dk
dev-seo4210.autodoc.dk 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: dev-seo4210.autodoc.dk
dev-seo4549.autodoc.dk 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: dev-seo4549.autodoc.dk
dev-seo4579.autodoc.dk 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: dev-seo4579.autodoc.dk
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: autodoc.dk
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: autodoc.dk
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: autodoc.dk

final https://autodoc.dk/status 403time 13msstack cloudflare

✗http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
✓Content-Security-Policy
default-src 'none'; script-src 'nonce-SOmCfcYDWzhmDot02a1G8P' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
same-origin
✓Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),micro
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

✓Receives mail via 4 servers
mailstream-central.mxrecord.mx mailstream-east.mxrecord.io mailstream-eu1.mxrecord.io mailstream-west.mxrecord.io
!SPFends in ~all
v=spf1 include:autodoc.dev ~all
✓DMARCp=quarantine
v=DMARC1;p=quarantine;pct=100;aspf=r;adkim=r;fo=1;ri=86400;rua=mailto:837bcc07d4bd40c39b39490962f3e4a9@dmarc-reports.cloudflare.net,mailto:dmarc-report@autodoc.dk
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
amir.ns.cloudflare.com dorthy.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
104.16.120.107 autodoc.dk +20	80443205220532082208320862087+4	0	Cloudflare~	—
104.16.119.107 autodoc.dk +20	80443208220832086208780808443+1	0	Cloudflare~	—

Archived URLs

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

autodoc.dk security report

Moderate

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames