magzdb.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 53 days left15 years old
30
magzdb.org was registered on 18 Nov 2010 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 18 Nov 2026. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org.
magzdb.org publishes 1 nameserver. DNSSEC is not signed.
magzdb.org has 1 IPv4 address (45.137.66.127). The geolocation database places 45.137.66.127 in Amsterdam, The Netherlands.
The TLS certificate from YR1 is not valid (TLS 1.2).
No safety warning was recorded for magzdb.org in the checks that ran.
Domain · RDAP/WHOIS
magzdb.org was registered on 18 Nov 2010 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 4 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org.
| Registered | since 18 Nov 2010 |
|---|---|
| Created | 18 November 2010 |
| Updated | 12 August 2026 |
| Expires | 18 November 2026 |
| Registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
| Status | client transfer prohibited |
| Nameservers | earth.orderbox-dns.com, mars.orderbox-dns.com, mercury.orderbox-dns.com, venus.orderbox-dns.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org |
magzdb.org 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.
Nameserver earth.orderbox-dns.com is published for magzdb.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org.
Nameserver mars.orderbox-dns.com is published for magzdb.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org.
Nameserver mercury.orderbox-dns.com is published for magzdb.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org.
Nameserver venus.orderbox-dns.com is published for magzdb.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org.
DNS
magzdb.org has 1 address record, 0 mail exchangers and 1 nameserver, measured at 1.1.1.1:53.
| A | 45.137.66.127 |
|---|---|
| AAAA | — |
| NS | irdns.mars.orderbox-dns.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 45.137.66.127 answers for magzdb.org at resolver 1.1.1.1:53.
Hosting and geo
magzdb.org is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 45.137.66.127 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for magzdb.org is not valid, with 53 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | booktracker.work |
| Valid from | 25 September 2026 |
| Valid until | 24 December 2026 |
| Days left | 53 |
| SAN count | 1 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: booktracker.work.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://magzdb.org/": tls: failed to verify certificate: x509: certificate is valid for booktracker.work, not magzdb.org
Security
Family DNS for magzdb.org 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 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 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
- October 2026: geo city changed from empty to Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is magzdb.org 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 magzdb.org?
magzdb.org is placed in Amsterdam, The Netherlands.
When does magzdb.org expire?
magzdb.org expires on 18 November 2026 according to https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org.
Who owns magzdb.org?
The registry did not return a person or a company for magzdb.org. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/magzdb.org at 2026-10-30T15:02:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:02:49Z
- TLS source tls:443 at 2026-10-30T15:02:49Z
- HTTP source https://magzdb.org/ at 2026-10-30T15:02:49Z
- Tech source not available at 2026-10-30T15:02:49Z
- Geo source db-ip at 2026-10-30T15:02:49Z
- Safety source family DNS and local lists at 2026-10-30T15:02: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.