Domain

assets.flodesk.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 assets.flodesk.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

240

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.

162.222.203.234:443 href · ×5

192.99.100.199:443 href · ×3

192.169.151.206:443 href · ×3

3.226.212.117:443 href · ×2

72.167.51.155:443 href · ×2

67.205.139.128:80 href · ×2

23.22.66.186:443 href · ×2

67.205.175.237:80 href · ×2

174.138.40.228:80 href · ×2

98.89.56.140:443 href · ×2

198.211.116.237:80 href · ×2

159.203.182.34:443 href · ×2

3.213.246.134:443 href · ×2

98.88.150.9:443 href · ×2

137.184.122.116:443 href · ×1

34.98.110.176:80 href · ×1

45.55.67.59:80 href · ×1

138.68.248.242:80 href · ×1

13.251.61.142:80 href · ×1

198.12.231.33:443 href · ×1

137.184.185.216:80 href · ×1

52.20.201.114:443 href · ×1

162.243.164.61:443 href · ×1

159.223.201.1:80 href · ×1

67.222.52.139:443 href · ×1

18.171.92.141:443 href · ×1

159.65.230.253:80 href · ×1

174.138.57.96:80 href · ×1

54.162.42.137:443 href · ×1

51.77.17.202:443 href · ×1

108.167.144.248:443 href · ×1

5.45.101.174:443 href · ×1

143.110.217.205:80 href · ×1

50.116.65.238:443 href · ×1

159.65.71.142:80 href · ×1

208.113.128.208:443 href · ×1

159.89.149.22:80 href · ×1

138.197.194.43:80 href · ×1

165.232.117.238:443 href · ×1

198.99.157.167:443 href · ×1

34.105.13.187:443 href · ×1

159.203.25.55:443 href · ×1

164.92.86.9:443 href · ×1

164.92.72.114:443 href · ×1

159.223.153.98:80 href · ×1

157.250.206.198:443 href · ×1

3.64.30.144:443 href · ×1

104.131.116.51:80 href · ×1

13.125.38.233:80 href · ×1

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