thumbs.pro

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200Family DNS blockedSSL: 21 days left8 years oldTranco #57096

One re-check per domain each UTC day.

55

thumbs.pro was registered on 12 Mar 2018 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 12 Mar 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/thumbs.pro.

thumbs.pro publishes 2 nameservers. DNSSEC is not signed.

thumbs.pro has 1 IPv4 address (162.244.32.72). The geolocation database places 162.244.32.72 in Santa Clara, United States.

The TLS certificate from YE2 is valid and has 21 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Nginx. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

thumbs.pro was registered on 12 Mar 2018 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/thumbs.pro.

Registeredsince 12 Mar 2018
Created12 March 2018
Updated12 August 2026
Expires12 March 2027
RegistrarPDR Ltd. d/b/a PublicDomainRegistry.com
Statusclient transfer prohibited
Nameserversns1.userporn.pro, ns2.userporn.pro
DNSSECno
Sourcehttps://rdap.identitydigital.services/rdap/domain/thumbs.pro

thumbs.pro 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 ns1.userporn.pro is published for thumbs.pro in the registration record from https://rdap.identitydigital.services/rdap/domain/thumbs.pro.

Nameserver ns2.userporn.pro is published for thumbs.pro in the registration record from https://rdap.identitydigital.services/rdap/domain/thumbs.pro.

DNS

thumbs.pro has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A162.244.32.72
AAAA—
NSns1.userporn.pro, ns2.userporn.pro
MX—
SPFpresent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at thumbs.pro is "v=spf1 -all".

IPv4 address 162.244.32.72 answers for thumbs.pro at resolver 1.1.1.1:53.

A random label under thumbs.pro also resolved, which means wildcard DNS is on.

Hosting and geo

thumbs.pro is placed in Santa Clara, United States by the local geolocation database (db-ip).

Address162.244.32.72
CountryUnited States
CitySanta Clara
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for thumbs.pro is valid, with 21 days left and 2 subject alternative names. Source: tls:443.

IssuerYE2
Subjectthumbs.pro
Valid from23 August 2026
Valid until21 November 2026
Days left21
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.thumbs.pro, thumbs.pro.

Tech stack

Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.

  • Nginx · Web servers, Reverse proxies

Nginx is filed under Web servers, Reverse proxies.

On-page checks

The homepage returned HTTP 200 in 155 ms. The target title is 10 characters and the page has 1 H1 heading.

Status200
TTFB155 ms
Title length10 yes
Quoted title"thumbs.pro"
Meta description"Archived NSFW Tumblr blogs" yes
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots metaall
Canonical—
Language—
Links55
Images36
Faviconno

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 thumbs.pro is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for thumbs.pro. 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 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 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

  • October 2026: geo city changed from empty to Santa Clara.
  • October 2026: geo country changed from empty to United States.

Questions

Is thumbs.pro safe?

Cloudflare family DNS returned a block for thumbs.pro. That resolver covers adult and malware names.

Who hosts thumbs.pro?

thumbs.pro is placed in Santa Clara, United States.

When does thumbs.pro expire?

thumbs.pro expires on 12 March 2027 according to https://rdap.identitydigital.services/rdap/domain/thumbs.pro.

Who owns thumbs.pro?

The registry did not return a person or a company for thumbs.pro. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.

Sources

  • RDAP source https://rdap.identitydigital.services/rdap/domain/thumbs.pro at 2026-10-30T15:56:52Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:56:52Z
  • TLS source tls:443 at 2026-10-30T15:56:52Z
  • HTTP source https://thumbs.pro/ at 2026-10-30T15:56:52Z
  • Tech source wappalyzergo at 2026-10-30T15:56:52Z
  • Geo source db-ip at 2026-10-30T15:56:52Z
  • Safety source family DNS and local lists at 2026-10-30T15:56:52Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.pro PDR Ltd. d/b/a PublicDomainRegistry.com

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.

Removal policy

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.