Domain

ascendoor.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 ascendoor.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

147.79.116.62, 185.77.97.150, 193.58.105.124, 195.200.9.217, 195.200.9.89, 2.57.91.1, 2.57.91.100, 2.57.91.116

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.

38.244.131.118:443 href · ×3

139.180.168.8:443 href · ×2

134.122.9.153:443 href · ×2

3.10.211.208:80 href · ×2

65.109.28.245:80 href · ×2

144.202.33.20:443 href · ×2

138.68.12.78:80 href · ×2

185.87.148.194:443 href · ×2

149.248.18.83:443 href · ×2

67.219.97.199:443 href · ×2

161.35.134.69:443 href · ×2

149.28.172.176:443 href · ×2

54.78.90.42:80 href · ×2

146.190.239.156:443 href · ×2

45.77.251.148:80 href · ×2

144.24.129.232:80 href · ×2

162.215.220.203:443 href · ×2

137.184.90.165:443 href · ×1

167.99.33.121:443 href · ×1

139.84.196.28:443 href · ×1

207.246.97.254:443 href · ×1

3.148.80.224:80 href · ×1

159.65.109.10:443 href · ×1

161.35.39.247:80 href · ×1

5.45.84.215:443 href · ×1

38.180.215.226:443 href · ×1

66.42.117.146:443 href · ×1

159.65.250.210:443 href · ×1

38.244.197.199:443 href · ×1

212.71.248.252:443 href · ×1

38.244.131.106:443 href · ×1

139.180.165.72:443 href · ×1

54.85.28.243:443 href · ×1

139.144.227.34:80 href · ×1

38.180.165.134:443 href · ×1

216.128.155.226:443 href · ×1

91.109.119.94:443 href · ×1

149.28.171.51:443 href · ×1

206.189.173.30:443 href · ×1

104.236.73.232:443 href · ×1

45.63.83.29:443 href · ×1

45.78.5.13:443 href · ×1

167.172.245.41:443 href · ×1

104.244.136.79:80 href · ×1

161.35.39.247:443 href · ×1

51.254.21.248:443 href · ×1

207.246.73.187:443 href · ×1

104.207.142.237:443 href · ×1

45.79.171.233:443 href · ×1

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