Domain

kit.fontawesome.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 kit.fontawesome.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.

185.119.117.2:443 href · ×17

89.35.129.195:80 href · ×11

207.154.225.109:443 href · ×8

107.174.181.56:80 href · ×6

34.82.127.100:443 href · ×6

129.21.16.82:443 href · ×6

178.134.60.55:8443 href · ×6

45.79.8.58:443 href · ×5

207.154.225.109:80 href · ×4

99.80.191.195:443 href · ×4

178.134.60.51:8443 href · ×4

69.163.140.59:443 href · ×4

129.212.240.212:80 href · ×4

205.251.155.112:443 href · ×4

3.33.150.216:443 href · ×4

195.201.153.115:443 href · ×4

69.163.202.244:443 href · ×4

103.124.169.16:80 href · ×4

172.105.87.4:80 href · ×4

178.134.60.49:8443 href · ×4

32.185.22.114:443 href · ×4

178.208.37.66:80 href · ×4

36.93.245.198:443 href · ×4

20.51.109.101:443 href · ×4

1.33.176.6:443 href · ×4

129.121.33.209:443 href · ×4

204.168.215.83:443 href · ×4

208.109.27.16:443 href · ×4

68.233.119.67:443 href · ×4

116.118.47.204:443 href · ×4

203.76.167.4:443 href · ×4

104.200.31.96:80 href · ×4

50.7.40.146:443 href · ×4

13.244.220.248:443 href · ×4

54.208.100.65:443 href · ×4

163.172.162.93:443 href · ×3

74.114.206.190:443 href · ×3

66.116.247.39:443 href · ×3

143.244.149.137:80 href · ×3

154.209.35.84:443 href · ×3

65.86.32.44:443 href · ×3

3.17.238.123:443 href · ×3

3.8.133.53:443 href · ×3

3.232.140.31:443 href · ×3

157.230.84.243:443 href · ×3

45.33.114.62:443 href · ×3

94.130.171.133:443 href · ×3

54.187.27.253:443 href · ×3

52.215.12.206:80 href · ×3

178.128.173.41:80 href · ×3

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.