mangafire.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 37 days left2 years oldTranco #7326
60
mangafire.to was registered on 2 Oct 2024 via Tonic and the registry expiry is 2 Oct 2028. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/mangafire.to.
mangafire.to publishes 2 nameservers. DNSSEC is not signed.
mangafire.to has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 37 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for mangafire.to in the checks that ran.
Domain · RDAP/WHOIS
mangafire.to was registered on 2 Oct 2024 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/mangafire.to.
| Registered | since 2 Oct 2024 |
|---|---|
| Created | 2 October 2024 |
| Updated | 7 August 2026 |
| Expires | 2 October 2028 |
| Registrar | Tonic |
| Status | active |
| Nameservers | aragorn.ns.cloudflare.com, brynne.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/mangafire.to |
Nameserver aragorn.ns.cloudflare.com is published for mangafire.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/mangafire.to.
Nameserver brynne.ns.cloudflare.com is published for mangafire.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/mangafire.to.
DNS
mangafire.to has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | aragorn.ns.cloudflare.com, brynne.ns.cloudflare.com |
| MX | — |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at mangafire.to is "v=spf1 include:spf.kingmailer.org ~all".
IPv4 address 188.114.96.3 answers for mangafire.to at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for mangafire.to at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for mangafire.to at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for mangafire.to at resolver 1.1.1.1:53.
A random label under mangafire.to also resolved, which means wildcard DNS is on.
Hosting and geo
mangafire.to is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for mangafire.to is valid, with 37 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | mangafire.to |
| Valid from | 8 September 2026 |
| Valid until | 7 December 2026 |
| Days left | 37 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.mangafire.to, mangafire.to.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 10 ms. The target title is 32 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 10 ms |
| Title length | 32 yes |
| Quoted title | "Attention Required! | Cloudflare" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex, nofollow |
| Canonical | — |
| Language | en-US |
| Links | 1 |
| Images | 0 |
| Favicon | no |
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 mangafire.to 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 10 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 5 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
- October 2026: dns aaaa changed from 2a06:98c1:3120::3,2a06:98c1:3121::3 to 2a06:98c1:3120::4,2a06:98c1:3121::4.
Questions
Is mangafire.to 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 mangafire.to?
mangafire.to is placed in Toronto, Canada.
When does mangafire.to expire?
mangafire.to expires on 2 October 2028 according to https://rdap.tonicregistry.to/rdap/domain/mangafire.to.
Who owns mangafire.to?
The registry did not return a person or a company for mangafire.to. RDAP often redacts the registrant. The registrar on file is Tonic.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/mangafire.to at 2026-10-30T15:16:21Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:16:21Z
- TLS source tls:443 at 2026-10-30T15:16:21Z
- HTTP source https://mangafire.to/ at 2026-10-30T15:16:21Z
- Tech source wappalyzergo at 2026-10-30T15:16:21Z
- Geo source db-ip at 2026-10-30T15:16:21Z
- Safety source family DNS and local lists at 2026-10-30T15:16:21Z
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.