papayads.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 57 days left6 years old
85
papayads.net was registered on 4 Apr 2020 via IONOS SE and the registry expiry is 4 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/papayads.net.
papayads.net publishes 2 nameservers. DNSSEC is not signed.
papayads.net has 2 IPv4 addresses (104.21.32.253, 172.67.157.39) and 2 IPv6 addresses (2606:4700:3033::ac43:9d27, 2606:4700:3036::6815:20fd). The geolocation database places 104.21.32.253 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 57 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Google AdSense, Google Ads, Google Ads Conversion Tracking, Google Analytics, HSTS, HTTP/3, Magnific Popup, PHP, WOW, jQuery and reCAPTCHA. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for papayads.net in the checks that ran.
Domain · RDAP/WHOIS
papayads.net was registered on 4 Apr 2020 via IONOS SE. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/papayads.net.
| Registered | since 4 Apr 2020 |
|---|---|
| Created | 4 April 2020 |
| Updated | 5 April 2026 |
| Expires | 4 April 2027 |
| Registrar | IONOS SE |
| Status | client transfer prohibited |
| Nameservers | finley.ns.cloudflare.com, rosalie.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/papayads.net |
papayads.net 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 finley.ns.cloudflare.com is published for papayads.net in the registration record from https://rdap.verisign.com/net/v1/domain/papayads.net.
Nameserver rosalie.ns.cloudflare.com is published for papayads.net in the registration record from https://rdap.verisign.com/net/v1/domain/papayads.net.
DNS
papayads.net has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.32.253, 172.67.157.39 |
|---|---|
| AAAA | 2606:4700:3033::ac43:9d27, 2606:4700:3036::6815:20fd |
| NS | finley.ns.cloudflare.com, rosalie.ns.cloudflare.com |
| MX | mx00.ionos.it (10), mx01.ionos.it (10) |
| 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 | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at papayads.net is "v=spf1 include:_spf-eu.ionos.com ~all".
The DMARC text record at _dmarc.papayads.net is "v=DMARC1; p=none;".
IPv4 address 104.21.32.253 answers for papayads.net at resolver 1.1.1.1:53.
IPv4 address 172.67.157.39 answers for papayads.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::ac43:9d27 answers for papayads.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:20fd answers for papayads.net at resolver 1.1.1.1:53.
Mail exchanger mx00.ionos.it has preference 10.
Mail exchanger mx01.ionos.it has preference 10.
Hosting and geo
papayads.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.32.253 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for papayads.net is valid, with 57 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | papayads.net |
| Valid from | 28 September 2026 |
| Valid until | 27 December 2026 |
| Days left | 57 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.papayads.net, papayads.net.
Tech stack
Tech detection checked the fetched homepage and named 13 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Cloudflare · CDN
- Google AdSense · Advertising
- Google Ads · Advertising
- Google Ads Conversion Tracking · Analytics
- Google Analytics · Analytics
- HSTS · Security
- HTTP/3 · Miscellaneous
- Magnific Popup · JavaScript libraries
- PHP · Programming languages
- WOW · JavaScript frameworks, Web frameworks, JavaScript graphics
- jQuery · JavaScript libraries
- reCAPTCHA · Security
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Google AdSense is filed under Advertising.
Google Ads is filed under Advertising.
Google Ads Conversion Tracking is filed under Analytics.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Magnific Popup is filed under JavaScript libraries.
PHP is filed under Programming languages.
WOW is filed under JavaScript frameworks, Web frameworks, JavaScript graphics.
jQuery is filed under JavaScript libraries.
reCAPTCHA is filed under Security.
On-page checks
The homepage returned HTTP 200 in 37 ms. The target title is 36 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 37 ms |
| Title length | 36 yes |
| Quoted title | "PapayAds - Maximize your ads revenue" |
| Meta description | "Maximize your ads revenue today keeping your current ads but enabling other networks to compete with your AdSense." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 27 |
| Images | 12 |
| 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 papayads.net 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 | yes |
| 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 15 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
First checked on 30 October 2026; changes will appear here.
Questions
Is papayads.net 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 papayads.net?
papayads.net is placed in Toronto, Canada.
When does papayads.net expire?
papayads.net expires on 4 April 2027 according to https://rdap.verisign.com/net/v1/domain/papayads.net.
Who owns papayads.net?
The registry did not return a person or a company for papayads.net. RDAP often redacts the registrant. The registrar on file is IONOS SE.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/papayads.net at 2026-10-30T14:54:39Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:54:39Z
- TLS source tls:443 at 2026-10-30T14:54:39Z
- HTTP source https://papayads.net/ at 2026-10-30T14:54:39Z
- Tech source wappalyzergo at 2026-10-30T14:54:39Z
- Geo source db-ip at 2026-10-30T14:54:39Z
- Safety source family DNS and local lists at 2026-10-30T14:54:39Z
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.