Domain

developers.openai.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 developers.openai.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

64.239.109.1, 64.239.109.129, 64.239.109.193, 64.239.109.65, 64.239.123.1, 64.239.123.129, 64.239.123.193, 64.239.123.65

AAAA

—

TXT

—

CNAME

—

CAA

0 issue "globalsign.com", 0 issue "letsencrypt.org", 0 issue "pki.goog", 0 issue "sectigo.com"

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

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

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

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

121.41.105.109:80 href · ×4

37.27.13.60:443 href · ×2

47.79.98.208:443 href · ×2

47.95.248.163:80 href · ×2

43.173.97.227:443 href · ×2

164.92.243.217:443 href · ×1

207.57.121.105:443 href · ×1

96.44.158.209:80 href · ×1

155.212.167.197:443 href · ×1

45.79.154.83:443 href · ×1

78.44.144.6:443 href · ×1

47.100.240.225:443 href · ×1

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.

3cf3ee2f0a14cc90… sectigo · elephant2026h1