Domain

www.medium.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 www.medium.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

—

AAAA

—

TXT

—

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

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.

46.229.224.228:80 href · ×2

142.93.153.67:80 href · ×2

119.59.98.141:443 href · ×1

43.153.25.177:443 href · ×1

38.54.23.210:80 href · ×1

104.225.146.54:443 href · ×1

23.224.212.252:443 href · ×1

202.43.102.40:443 href · ×1

23.225.143.53:443 href · ×1

38.54.63.83:80 href · ×1

142.4.112.45:443 href · ×1

35.228.181.233:80 href · ×1

134.122.184.66:443 href · ×1

137.175.14.123:443 href · ×1

135.125.210.186:443 href · ×1

146.70.53.212:443 href · ×1

65.20.105.211:80 href · ×1

104.233.222.143:443 href · ×1

23.225.190.51:443 href · ×1

198.16.36.70:443 href · ×1

103.124.95.63:443 href · ×1

108.181.136.19:443 href · ×1

104.233.235.228:443 href · ×1

198.2.210.129:443 href · ×1

103.137.62.180:443 href · ×1

65.20.103.190:80 href · ×1

38.54.104.187:80 href · ×1

146.70.53.220:443 href · ×1

137.175.35.14:443 href · ×1

23.225.187.210:443 href · ×1

137.175.11.109:443 href · ×1

23.225.187.212:443 href · ×1

107.148.248.18:443 href · ×1

23.225.143.39:443 href · ×1

38.60.156.5:80 href · ×1

23.224.143.157:443 href · ×1

38.60.200.195:80 href · ×1

119.59.98.138:443 href · ×1

23.225.190.58:443 href · ×1

104.233.223.3:443 href · ×1

185.213.23.93:443 href · ×1

45.55.238.77:443 href · ×1

103.140.127.192:443 href · ×1

51.195.9.22:443 href · ×1

137.220.142.72:443 href · ×1

137.220.142.93:443 href · ×1

167.172.210.45:80 href · ×1

23.225.143.60:443 href · ×1

107.148.193.93:443 href · ×1

137.175.11.106: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.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.