self.network
Monitoring only
Cloudflare self.network
DNS, hosting, email and name analysis are live. Registration data, the home-page probe, the archive lookup and the other-TLD check are being fetched in the background; this page refreshes itself in a few seconds.
Registration
Fetching the registry record…
DNS
| Type | Value |
|---|---|
| NS | leah.ns.cloudflare.com · phil.ns.cloudflare.com |
| A | 104.21.59.201 |
| A | 172.67.183.133 |
| AAAA | 2606:4700:3030::6815:3bc9 |
| AAAA | 2606:4700:3033::ac43:b785 |
| MX | 10 mail.self.network |
| TXT | google-site-verification=HgkgBLUbVbplhUcq6RtO2vQyQ02jkX4d0Xl6B0TfSUs |
| TXT | v=spf1 mx ~all |
| SOA | leah.ns.cloudflare.com dns.cloudflare.com serial 2415387030 |
Certificates
No certificate for this domain has passed through the logs dot.bi follows since it started watching. Older certificates are not back-filled.
Hosting
- IP
- 104.21.59.201
- Network
- AS13335 · CLOUDFLARENET - Cloudflare, Inc., US
- Provider
- Cloudflare
- Country
- US (network registration, not server location)
- CDN
- none detected
- IPv6
- yes
Web
Probing the home page…
Monitoring only DMARC is set to p=none: spoofed mail is reported but still delivered.
- Provider
- self.network
- SPF
- present all: softfail
- DMARC
- p=none reports on
- DKIM
- not found common selectors only
Age
- First capture
- looking up…
- Years archived
- —
- Registry created
- —
- In dot.bi since
- 2026-10-13 · Zone file
Name analysis
Same name, other TLDs
Checking the same name on other TLDs…