dotpe.in security report

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

60risk

Elevated

Several issues worth triaging this week.

1Critical

0High

1Medium

6Low

2Info

Collected 21 hours ago31.7sfrom cache

Certificate Transparency10
DNS resolution23
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs34
Registration
DNS posture4
Email authentication2
Certificate
Security headers6
Archived URLs
Analysis10

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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 3.111.112.55 (gitlab.dotpe.in), which advertise python 3.12. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-7210 CVE-2026-6019 CVE-2026-4519 CVE-2026-3644 CVE-2026-3087 CVE-2025-13837 CVE-2025-13462 CVE-2025-12781 CVE-2025-12084 CVE-2021-32052 CVE-2020-29396 CVE-2009-3720 CVE-2009-2940
What to do
Confirm the running versions on 3.111.112.55 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-7210 ↗CVE-2026-6019 ↗CVE-2026-4519 ↗CVE-2026-3644 ↗CVE-2026-3087 ↗
asset: 3.111.112.55
3.111.112.55 (gitlab.dotpe.in) reports python 3.12. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 3.111.112.55
gitlab.dotpe.in 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.dotpe.in
dev.dotpe.in 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.dotpe.in
stage.dotpe.in 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.dotpe.in
internal.dotpe.in 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.dotpe.in
internal.shared.dotpe.in 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.shared.dotpe.in
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: dotpe.in
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: dotpe.in
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: dotpe.in

final https://dotpe.in/status 200time 368msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000
✓Content-Security-Policy
default-src 'self'; script-src 'self' 'unsafe-inline' https://code.jquery.com https://cdnjs.cloudflare.com https://cdn.jsdelivr.net https://maxcdn.bootstrapcdn.…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
✓Permissions-Policy
geolocation=(self)
–security.txt publishedoptional — tells researchers where to report bugs

✓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:1278314a1.spf2.netcorecloud.net include:transmail.net.in include:zcsend.in -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1182.awsdns-19.org ns-1975.awsdns-54.co.uk ns-391.awsdns-48.com ns-955.awsdns-55.net

✓Registered with GoDaddy7.2 years old
dotpe.in
✓Registration expiry1388 days
2030-06-26
✓Transfer lock
client transfer prohibited, client renew prohibited, client update prohibited, client delete prohibited
✓4 nameservers at registry
ns-1182.awsdns-19.org ns-1975.awsdns-54.co.uk ns-391.awsdns-48.com ns-955.awsdns-55.net

Address	Ports	CVEs	Edge	Network
162.159.140.147 status.dotpe.in +3	80443205220532082208320862087+5	0	Cloudflare~	—
172.66.0.145 status.dotpe.in +3	80443205220532082208320862087+5	0	Cloudflare~	—
13.205.213.90 dotpe.in +5	80443	0	direct	—
3.111.112.55 gitlab.dotpe.in +2	80443	13	direct	—
3.109.95.106 gitlab.dotpe.in +3	80443	0	direct	—
35.154.237.203 dotpe.in +5	443	0	direct	—
35.154.155.169 gitlab.dotpe.in +3	443	0	direct	—
65.1.116.196 dotpe.in +4	none known	0	direct	—

Archived URLs

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

dotpe.in security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames