Domain

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

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
teamupdraft.com	104.26.0.149 2606:4700:20::681a:95 2606:4700:20::ac43:44b9 2606:4700:20::681a:195 +2	2026-07-28 20:47:52.650
bf-staging.teamupdraft.com		1970-01-01 00:00:00.000
gvstaging.teamupdraft.com		1970-01-01 00:00:00.000
matomo.teamupdraft.com		1970-01-01 00:00:00.000
monitoring-int.teamupdraft.com		1970-01-01 00:00:00.000
www.teamupdraft.com		1970-01-01 00:00:00.000

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.

154.204.143.82:443 href · ×2

178.62.214.179:443 href · ×2

146.190.19.210:443 href · ×1

51.254.236.43:80 href · ×1

92.205.23.18:443 href · ×1

203.162.234.89:80 href · ×1

154.204.137.68:443 href · ×1

38.242.206.72:80 href · ×1

64.13.224.141:443 href · ×1

148.72.24.83:443 href · ×1

50.6.227.230:443 href · ×1

1.201.18.27:443 href · ×1

20.245.210.8:80 href · ×1

103.45.244.15:443 href · ×1

85.238.112.102:443 href · ×1

60.43.193.101:80 href · ×1

162.213.248.87:443 href · ×1

118.142.52.42:80 href · ×1

137.184.244.239:443 href · ×1

72.167.211.222:80 href · ×1

83.228.215.81:443 href · ×1

46.105.252.19:443 href · ×1

212.36.2.60:443 href · ×1

210.150.59.104:443 href · ×1

132.148.208.113:443 href · ×1

65.21.48.127:443 href · ×1

85.215.83.211:443 href · ×1

121.40.249.73:80 href · ×1

208.109.60.225:443 href · ×1

158.178.198.45:443 href · ×1

216.146.211.103:443 href · ×1

103.235.105.227:443 href · ×1

134.209.253.136:443 href · ×1

35.209.106.191:443 href · ×1

43.252.167.33:443 href · ×1

139.144.235.88:443 href · ×1

34.125.10.202:80 href · ×1

66.39.150.230:443 href · ×1

77.73.71.191:80 href · ×1

195.201.252.25:80 href · ×1

50.87.30.174:443 href · ×1

54.38.58.96:443 href · ×1

70.40.215.123:443 href · ×1

104.244.127.210:80 href · ×1

132.248.31.80:443 href · ×1

68.178.246.25:80 href · ×1

167.160.191.200:443 href · ×1

162.241.155.5:443 href · ×1

206.189.7.204:443 href · ×1

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