Domain

dr-40.com

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of dr-40.com

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now

Hosting IPs

—

A/AAAA targets

Subdomains

—

CT + scan + body

Record Types

—

seen in DNS

Observed Certs

—

in our scans

DNS Records

203.141.53.27

AAAA

—

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-1506.awsdns-60.org, ns-1815.awsdns-34.co.uk, ns-426.awsdns-53.com, ns-944.awsdns-54.net

TXT

facebook-domain-verification=u0tgmx0v7xudezuq1camvtkr0iuqf1, google-site-verification=ZRNOkLOhoHnOHQW8Wt-68wxGZdtya1_wB4LXuyvpUSs, v=spf1 +ip4:210.140.76.243 +ip4:210.140.76.238 +ip4:210.140.79.204 +include:_spf.google.com ~all

CNAME

—

CAA

—

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain	Resolves to	Last seen
dev.dr-40.com		1970-01-01 00:00:00.000
dr-40.com	203.141.53.27	2026-06-17 07:35:59.279
stg.dr-40.com		1970-01-01 00:00:00.000
www.dr-40.com	203.141.53.27	2026-06-17 07:35:59.279

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

3d49d8a0864d194f… google · argon2026h1

Subject: www.dr-40.com

Issuer: GlobalSign GCC R3 DV TLS CA 2020