bfix.bf
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of bfix.bf
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
DNS Records
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 |
|---|---|---|
| bfix-oua-manager.bfix.bf | 2026-06-23 04:13:54.296 | |
| bfixmanager.bfix.bf | 2026-07-17 20:40:10.303 | |
| collabora.bfix.bf | 1970-01-01 00:00:00.000 | |
| drive.bfix.bf | 2026-07-17 12:46:11.114 | |
| jami.bfix.bf | 2026-07-24 10:20:52.883 | |
| lg.bfix.bf | 2026-07-26 05:10:09.175 | |
| monitoring.bfix.bf | 2026-06-23 04:39:02.400 | |
| monitoring2.bfix.bf | 1970-01-01 00:00:00.000 | |
| nextcloud.bfix.bf | 2026-07-17 12:46:11.114 | |
| training.bfix.bf | 2026-07-15 19:40:12.781 | |
| www.bfix-oua-manager.bfix.bf | 2026-06-23 04:13:54.296 | |
| www.bfixmanager.bfix.bf | 2026-07-17 20:40:10.303 | |
| www.drive.bfix.bf | 2026-07-17 12:46:11.114 | |
| www.jami.bfix.bf | 2026-07-24 10:20:52.883 | |
| www.lg.bfix.bf | 2026-07-26 05:10:09.175 | |
| www.monitoring.bfix.bf | 2026-06-23 04:39:02.400 | |
| www.nextcloud.bfix.bf | 2026-07-17 12:46:11.114 |
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
No citing IPs found yet
As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.
Origin / IP-Leak
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.