Check-Host.cc

Domain

f-tpl.com

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of f-tpl.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
2
A/AAAA targets
Subdomains
11
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
2
in our scans

DNS Records

A
118.27.125.151, 163.44.185.215
AAAA
MX
10 mx01.lolipop.jp
NS
uns01.lolipop.jp, uns02.lolipop.jp
TXT
v=spf1 include:_spf.lolipop.jp ~all
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
f-tpl.com 2026-07-28 19:57:26.855

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.

61.112.15.177:443 href · ×9
111.101.127.36:80 href · ×6
119.245.153.154:80 href · ×6
122.28.58.249:80 href · ×6
61.126.56.188:443 href · ×4
140.227.88.245:80 href · ×4
210.190.171.39:80 href · ×4
60.43.208.179:80 href · ×4
118.27.7.22:443 href · ×3
3.107.86.137:80 href · ×3
140.227.146.156:443 href · ×3
162.43.18.182:443 href · ×3
164.70.120.160:443 href · ×3
160.16.118.59:80 href · ×3
122.28.56.208:443 href · ×3
13.193.228.183:443 href · ×3
122.28.35.22:80 href · ×3
116.80.110.14:443 href · ×3
180.222.84.247:80 href · ×3
85.131.213.214:80 href · ×3
218.40.197.142:443 href · ×3
133.242.147.200:443 href · ×3
150.31.134.82:80 href · ×3
125.206.178.79:80 href · ×3
61.112.15.177:80 href · ×3
210.236.51.118:443 href · ×3
122.28.34.53:80 href · ×3
153.121.33.172:443 href · ×3
153.126.131.38:80 href · ×3
133.6.82.76:443 href · ×3
61.126.57.21:443 href · ×3
122.28.38.54:443 href · ×3
133.1.160.61:80 href · ×3
110.50.206.224:80 href · ×3
54.64.114.243:443 href · ×2
18.182.153.37:80 href · ×2
60.43.213.177:443 href · ×2
1.33.168.137:80 href · ×2
54.248.67.238:80 href · ×2
157.205.5.22:80 href · ×2
60.43.201.207:80 href · ×2
60.43.153.126:80 href · ×2
153.122.140.72:80 href · ×2
116.80.12.171:80 href · ×2
161.34.2.172:80 href · ×2
202.214.43.34:80 href · ×2
182.48.13.222:443 href · ×2
210.154.206.43:80 href · ×2
160.16.124.212:443 href · ×2
150.60.243.242:443 href · ×2

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

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
NS uns01.lolipop.jp 2026-05-26 02:38:03.884 2026-07-28 19:57:26.855
A 163.44.185.215 2026-05-26 02:38:03.884 2026-06-23 00:23:05.472
MX 10 mx01.lolipop.jp 2026-05-26 02:38:03.884 2026-07-28 19:57:26.855
TXT v=spf1 include:_spf.lolipop.jp ~all 2026-05-26 02:38:03.884 2026-07-28 19:57:26.855
NS uns02.lolipop.jp 2026-05-26 02:38:03.884 2026-07-28 19:57:26.855
A 118.27.125.151 2026-07-16 19:18:05.715 2026-07-28 19:57:26.855