fanfox.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 57 days left8 years oldTranco #7834
70
fanfox.net was registered on 29 Jan 2018 via GoDaddy.com, LLC and the registry expiry is 29 Jan 2028. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/fanfox.net.
fanfox.net publishes 2 nameservers. DNSSEC is not signed.
fanfox.net has 2 IPv4 addresses (104.21.48.63, 172.67.179.214) and 2 IPv6 addresses (2606:4700:3035::ac43:b3d6, 2606:4700:3037::6815:303f). The geolocation database places 104.21.48.63 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 57 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google Analytics, HTTP/3, Microsoft ASP.NET, Swiper and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for fanfox.net in the checks that ran.
Domain · RDAP/WHOIS
fanfox.net was registered on 29 Jan 2018 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/fanfox.net.
| Registered | since 29 Jan 2018 |
|---|---|
| Created | 29 January 2018 |
| Updated | 16 October 2026 |
| Expires | 29 January 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | gene.ns.cloudflare.com, nick.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/fanfox.net |
fanfox.net carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
fanfox.net carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
fanfox.net carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
fanfox.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver gene.ns.cloudflare.com is published for fanfox.net in the registration record from https://rdap.verisign.com/net/v1/domain/fanfox.net.
Nameserver nick.ns.cloudflare.com is published for fanfox.net in the registration record from https://rdap.verisign.com/net/v1/domain/fanfox.net.
DNS
fanfox.net has 4 address records, 4 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.48.63, 172.67.179.214 |
|---|---|
| AAAA | 2606:4700:3035::ac43:b3d6, 2606:4700:3037::6815:303f |
| NS | gene.ns.cloudflare.com, nick.ns.cloudflare.com |
| MX | smtp.secureserver.net (0) GoDaddy, mxbiz2.qq.com (5), mailstore1.secureserver.net (10) GoDaddy, mxbiz1.qq.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at fanfox.net is "v=spf1 include:secureserver.net -all".
IPv4 address 104.21.48.63 answers for fanfox.net at resolver 1.1.1.1:53.
IPv4 address 172.67.179.214 answers for fanfox.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::ac43:b3d6 answers for fanfox.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::6815:303f answers for fanfox.net at resolver 1.1.1.1:53.
Mail exchanger smtp.secureserver.net has preference 0. The host is recognised as GoDaddy.
Mail exchanger mxbiz2.qq.com has preference 5.
Mail exchanger mailstore1.secureserver.net has preference 10. The host is recognised as GoDaddy.
Mail exchanger mxbiz1.qq.com has preference 10.
Hosting and geo
fanfox.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.48.63 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for fanfox.net is valid, with 57 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | fanfox.net |
| Valid from | 28 September 2026 |
| Valid until | 27 December 2026 |
| Days left | 57 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.fanfox.net, fanfox.net.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
- Microsoft ASP.NET · Web frameworks
- Swiper · JavaScript libraries
- jQuery · JavaScript libraries
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
Microsoft ASP.NET is filed under Web frameworks.
Swiper is filed under JavaScript libraries.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 297 ms. The target title is 39 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 297 ms |
| Title length | 39 yes |
| Quoted title | "Manga Fox - Read Manga Online for Free!" |
| Meta description | "Read your favorite manga online! Hundreds of high-quality free manga for you, with a list being updated daily. Naruto manga, Bleach manga, One Piece manga, Air Gear manga, Claymore manga, Fairy Tail manga, Inuyasha manga, and many more..." yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://fanfox.net/ |
| Language | en |
| Links | 225 |
| Images | 288 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for fanfox.net is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is fanfox.net safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts fanfox.net?
fanfox.net is placed in Toronto, Canada.
When does fanfox.net expire?
fanfox.net expires on 29 January 2028 according to https://rdap.verisign.com/net/v1/domain/fanfox.net.
Who owns fanfox.net?
The registry did not return a person or a company for fanfox.net. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/fanfox.net at 2026-10-30T14:51:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:51:49Z
- TLS source tls:443 at 2026-10-30T14:51:49Z
- HTTP source https://fanfox.net/ at 2026-10-30T14:51:49Z
- Tech source wappalyzergo at 2026-10-30T14:51:49Z
- Geo source db-ip at 2026-10-30T14:51:49Z
- Safety source family DNS and local lists at 2026-10-30T14:51:49Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.