mangafox.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 52 days left19 years oldTranco #865378
70
mangafox.com was registered on 8 Oct 2007 via GoDaddy.com, LLC and the registry expiry is 8 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/mangafox.com.
mangafox.com publishes 2 nameservers. DNSSEC is not signed.
mangafox.com has 2 IPv4 addresses (104.21.63.248, 172.67.173.99) and 2 IPv6 addresses (2606:4700:3031::6815:3ff8, 2606:4700:3033::ac43:ad63). The geolocation database places 104.21.63.248 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 52 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 mangafox.com in the checks that ran.
Domain · RDAP/WHOIS
mangafox.com was registered on 8 Oct 2007 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/mangafox.com.
| Registered | since 8 Oct 2007 |
|---|---|
| Created | 8 October 2007 |
| Updated | 9 July 2026 |
| Expires | 8 October 2027 |
| 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/com/v1/domain/mangafox.com |
mangafox.com 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.
mangafox.com 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.
mangafox.com 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.
mangafox.com 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 mangafox.com in the registration record from https://rdap.verisign.com/com/v1/domain/mangafox.com.
Nameserver nick.ns.cloudflare.com is published for mangafox.com in the registration record from https://rdap.verisign.com/com/v1/domain/mangafox.com.
DNS
mangafox.com has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.63.248, 172.67.173.99 |
|---|---|
| AAAA | 2606:4700:3031::6815:3ff8, 2606:4700:3033::ac43:ad63 |
| NS | gene.ns.cloudflare.com, nick.ns.cloudflare.com |
| MX | mxbiz1.qq.com (5), mxbiz2.qq.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at mangafox.com is "v=spf1 a mx a:noez.net include:smtp2go.com ~all".
IPv4 address 104.21.63.248 answers for mangafox.com at resolver 1.1.1.1:53.
IPv4 address 172.67.173.99 answers for mangafox.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::6815:3ff8 answers for mangafox.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::ac43:ad63 answers for mangafox.com at resolver 1.1.1.1:53.
Mail exchanger mxbiz1.qq.com has preference 5.
Mail exchanger mxbiz2.qq.com has preference 10.
Hosting and geo
mangafox.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.63.248 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for mangafox.com is valid, with 52 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | mangafox.com |
| Valid from | 23 September 2026 |
| Valid until | 23 December 2026 |
| Days left | 52 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.mangafox.com, mangafox.com.
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 359 ms. The target title is 39 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 359 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 | http://fanfox.net/ |
| Language | en |
| Links | 226 |
| 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 mangafox.com 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 mangafox.com 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 mangafox.com?
mangafox.com is placed in Toronto, Canada.
When does mangafox.com expire?
mangafox.com expires on 8 October 2027 according to https://rdap.verisign.com/com/v1/domain/mangafox.com.
Who owns mangafox.com?
The registry did not return a person or a company for mangafox.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/mangafox.com at 2026-10-30T14:03:02Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:03:02Z
- TLS source tls:443 at 2026-10-30T14:03:02Z
- HTTP source https://mangafox.com/ at 2026-10-30T14:03:02Z
- Tech source wappalyzergo at 2026-10-30T14:03:02Z
- Geo source db-ip at 2026-10-30T14:03:02Z
- Safety source family DNS and local lists at 2026-10-30T14:03:02Z
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.