pdfroom.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 88 days left6 years oldTranco #116933
75
pdfroom.com was registered on 5 May 2020 via Tucows Domains Inc. and the registry expiry is 5 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/pdfroom.com.
pdfroom.com publishes 2 nameservers. DNSSEC is signed.
pdfroom.com has 3 IPv4 addresses (104.26.0.78, 104.26.1.78, 172.67.72.99) and 3 IPv6 addresses (2606:4700:20::681a:14e, 2606:4700:20::681a:4e, 2606:4700:20::ac43:4863). The geolocation database places 104.26.0.78 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Alpine.js, Cloudflare, Cloudflare Browser Insights, Google Analytics and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
pdfroom.com was registered on 5 May 2020 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/pdfroom.com.
| Registered | since 5 May 2020 |
|---|---|
| Created | 5 May 2020 |
| Updated | 5 April 2026 |
| Expires | 5 May 2027 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | alan.ns.cloudflare.com, michelle.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/pdfroom.com |
pdfroom.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.
pdfroom.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 alan.ns.cloudflare.com is published for pdfroom.com in the registration record from https://rdap.verisign.com/com/v1/domain/pdfroom.com.
Nameserver michelle.ns.cloudflare.com is published for pdfroom.com in the registration record from https://rdap.verisign.com/com/v1/domain/pdfroom.com.
DNS
pdfroom.com has 6 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.0.78, 104.26.1.78, 172.67.72.99 |
|---|---|
| AAAA | 2606:4700:20::681a:14e, 2606:4700:20::681a:4e, 2606:4700:20::ac43:4863 |
| NS | alan.ns.cloudflare.com, michelle.ns.cloudflare.com |
| MX | route3.mx.cloudflare.net (38), route1.mx.cloudflare.net (60), route2.mx.cloudflare.net (71) |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at pdfroom.com is "v=spf1 include:_spf.mx.cloudflare.net -all".
The DMARC text record at _dmarc.pdfroom.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.26.0.78 answers for pdfroom.com at resolver 1.1.1.1:53.
IPv4 address 104.26.1.78 answers for pdfroom.com at resolver 1.1.1.1:53.
IPv4 address 172.67.72.99 answers for pdfroom.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:14e answers for pdfroom.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:4e answers for pdfroom.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4863 answers for pdfroom.com at resolver 1.1.1.1:53.
Mail exchanger route3.mx.cloudflare.net has preference 38.
Mail exchanger route1.mx.cloudflare.net has preference 60.
Mail exchanger route2.mx.cloudflare.net has preference 71.
Hosting and geo
pdfroom.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.0.78 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for pdfroom.com is valid, with 88 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | pdfroom.com |
| Valid from | 30 October 2026 |
| Valid until | 28 January 2027 |
| Days left | 88 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.pdfroom.com, pdfroom.com.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Alpine.js · JavaScript frameworks
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
Alpine.js is filed under JavaScript frameworks.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 252 ms. The target title is 43 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 252 ms |
| Title length | 43 yes |
| Quoted title | "PDF Room - Your Search Engine For Free PDFs" |
| Meta description | "The PDF Room search engine allows you to find the best educational and recreational PDFs online. Browse through high-quality PDFs from trusted sources." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://pdfroom.com |
| Language | en |
| Links | 224 |
| Images | 44 |
| 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 pdfroom.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for pdfroom.com. That resolver covers adult and malware names.
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 20 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 0 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 pdfroom.com safe?
Cloudflare family DNS returned a block for pdfroom.com. That resolver covers adult and malware names.
Who hosts pdfroom.com?
pdfroom.com is placed in Toronto, Canada.
When does pdfroom.com expire?
pdfroom.com expires on 5 May 2027 according to https://rdap.verisign.com/com/v1/domain/pdfroom.com.
Who owns pdfroom.com?
The registry did not return a person or a company for pdfroom.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/pdfroom.com at 2026-10-30T14:08:57Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:08:57Z
- TLS source tls:443 at 2026-10-30T14:08:57Z
- HTTP source https://pdfroom.com/ at 2026-10-30T14:08:57Z
- Tech source wappalyzergo at 2026-10-30T14:08:57Z
- Geo source db-ip at 2026-10-30T14:08:57Z
- Safety source family DNS and local lists at 2026-10-30T14:08:57Z
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.