plentyrx.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 84 days left8 years old
75
plentyrx.com was registered on 18 Jan 2018 via GoDaddy.com, LLC and the registry expiry is 18 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/plentyrx.com.
plentyrx.com publishes 2 nameservers. DNSSEC is not signed.
plentyrx.com has 1 IPv4 address (3.136.62.64). The geolocation database places 3.136.62.64 in Dublin, United States.
The TLS certificate from YR1 is valid and has 84 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Bootstrap, Google Analytics, IIS, Microsoft ASP.NET, Windows Server, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for plentyrx.com in the checks that ran.
Domain · RDAP/WHOIS
plentyrx.com was registered on 18 Jan 2018 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/plentyrx.com.
| Registered | since 18 Jan 2018 |
|---|---|
| Created | 18 January 2018 |
| Updated | 18 January 2026 |
| Expires | 18 January 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns67.domaincontrol.com, ns68.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/plentyrx.com |
plentyrx.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.
plentyrx.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.
plentyrx.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.
plentyrx.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 ns67.domaincontrol.com is published for plentyrx.com in the registration record from https://rdap.verisign.com/com/v1/domain/plentyrx.com.
Nameserver ns68.domaincontrol.com is published for plentyrx.com in the registration record from https://rdap.verisign.com/com/v1/domain/plentyrx.com.
DNS
plentyrx.com has 1 address record, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 3.136.62.64 |
|---|---|
| AAAA | — |
| NS | ns67.domaincontrol.com, ns68.domaincontrol.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at plentyrx.com is "v=spf1 include:zcsend.net ~all".
The DMARC text record at _dmarc.plentyrx.com is "v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; sp=none; aspf=r;".
IPv4 address 3.136.62.64 answers for plentyrx.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
plentyrx.com is placed in Dublin, United States by the local geolocation database (db-ip).
| Address | 3.136.62.64 |
|---|---|
| Country | United States |
| City | Dublin |
| Source | db-ip |
SSL/TLS
The certificate for plentyrx.com is valid, with 84 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | plentyrx.com |
| Valid from | 26 October 2026 |
| Valid until | 24 January 2027 |
| Days left | 84 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: plentyrx.com, www.plentyrx.com.
Tech stack
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Google Analytics · Analytics
- IIS · Web servers
- Microsoft ASP.NET · Web frameworks
- Windows Server · Operating systems
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Bootstrap is filed under UI frameworks.
Google Analytics is filed under Analytics.
IIS is filed under Web servers.
Microsoft ASP.NET is filed under Web frameworks.
Windows Server is filed under Operating systems.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 113 ms. The target title is 15 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 113 ms |
| Title length | 15 yes |
| Quoted title | "PlentyRx - Home" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 32 |
| Images | 1 |
| 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 plentyrx.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 10 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 Dublin.
- October 2026: geo country changed from empty to United States.
Questions
Is plentyrx.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 plentyrx.com?
plentyrx.com is placed in Dublin, United States.
When does plentyrx.com expire?
plentyrx.com expires on 18 January 2027 according to https://rdap.verisign.com/com/v1/domain/plentyrx.com.
Who owns plentyrx.com?
The registry did not return a person or a company for plentyrx.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/plentyrx.com at 2026-10-30T14:09:38Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:09:38Z
- TLS source tls:443 at 2026-10-30T14:09:38Z
- HTTP source https://plentyrx.com/ at 2026-10-30T14:09:38Z
- Tech source wappalyzergo at 2026-10-30T14:09:38Z
- Geo source db-ip at 2026-10-30T14:09:38Z
- Safety source family DNS and local lists at 2026-10-30T14:09:38Z
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.