Domain

helpx.adobe.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 helpx.adobe.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

104.109.143.20, 104.109.143.7, 184.24.77.36, 184.24.77.39, 2.16.10.166, 2.16.10.167, 2.16.10.171, 2.16.10.177

AAAA

2600:141b:1c00:2a04::17d2:4959, 2600:141b:1c00:2a0c::17d2:5cc8, 2600:141b:1c00:30::1739:5a68, 2600:141b:1c00:30::1739:5a69, 2a02:26f0:1180:71::210:6a0a, 2a02:26f0:1180:71::210:6a0e, 2a02:26f0:1180:71::210:6a1f, 2a02:26f0:1180:71::210:6a21

—

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.

18.180.0.69:80 href · ×87

109.248.157.220:465 href · ×4

109.248.157.220:995 href · ×4

109.248.157.220:443 href · ×4

139.59.202.162:80 href · ×3

13.229.28.26:443 href · ×2

106.14.140.11:80 href · ×2

124.93.160.14:80 href · ×2

188.166.171.219:443 href · ×2

130.248.148.140:80 href · ×2

142.93.3.77:443 href · ×2

67.59.185.208:443 href · ×2

23.21.242.34:80 href · ×2

192.241.156.98:80 href · ×2

193.198.203.200:80 href · ×2

116.52.157.182:8080 href · ×2

192.33.1.31:80 href · ×2

34.94.137.181:80 href · ×2

54.251.224.73:80 href · ×2

210.230.223.53:80 href · ×2

35.221.129.187:443 href · ×2

46.62.222.231:443 href · ×2

128.122.118.13:443 href · ×2

88.208.4.234:443 href · ×2

193.198.203.213:443 href · ×2

59.153.28.18:80 href · ×2

50.194.42.82:80 href · ×2

13.114.169.255:443 href · ×2

199.184.160.51:443 href · ×2

63.140.45.165:443 href · ×2

193.198.203.211:8080 href · ×2

59.46.226.142:80 href · ×2

35.75.173.86:443 href · ×2

18.139.130.252:443 href · ×2

216.218.116.62:80 href · ×2

82.223.8.169:443 href · ×2

15.206.189.165:443 href · ×2

109.248.157.220:9443 href · ×2

128.122.118.13:80 href · ×2

34.94.137.181:443 href · ×2

128.122.122.26:443 href · ×2

64.202.191.147:443 href · ×1

91.244.253.86:8080 href · ×1

133.242.54.87:443 href · ×1

98.91.204.6:443 href · ×1

103.112.184.135:80 href · ×1

52.30.17.69:8443 href · ×1

153.122.157.210:80 href · ×1

63.178.115.156:443 href · ×1

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