adinplay.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 88 days left13 years oldTranco #62875
90
adinplay.com was registered on 4 Dec 2012 via Amazon Registrar, Inc. and the registry expiry is 4 Dec 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/adinplay.com.
adinplay.com publishes 2 nameservers. DNSSEC is not signed.
adinplay.com has 1 IPv4 address (198.202.211.1) and 1 IPv6 address (2620:cb:2000::1). The geolocation database places 198.202.211.1 in San Francisco (South of Market), United States.
The TLS certificate from WE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Google Analytics, Google Font API, Google Hosted Libraries, Google Tag Manager, HSTS, HTTP/3, jQuery and jsDelivr. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for adinplay.com in the checks that ran.
Domain · RDAP/WHOIS
adinplay.com was registered on 4 Dec 2012 via Amazon Registrar, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/adinplay.com.
| Registered | since 4 Dec 2012 |
|---|---|
| Created | 4 December 2012 |
| Updated | 30 October 2026 |
| Expires | 4 December 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | client transfer prohibited |
| Nameservers | beau.ns.cloudflare.com, elaine.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/adinplay.com |
adinplay.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.
Nameserver beau.ns.cloudflare.com is published for adinplay.com in the registration record from https://rdap.verisign.com/com/v1/domain/adinplay.com.
Nameserver elaine.ns.cloudflare.com is published for adinplay.com in the registration record from https://rdap.verisign.com/com/v1/domain/adinplay.com.
DNS
adinplay.com has 2 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 198.202.211.1 |
|---|---|
| AAAA | 2620:cb:2000::1 |
| NS | beau.ns.cloudflare.com, elaine.ns.cloudflare.com |
| MX | aspmx.l.google.com (10) Google, alt1.aspmx.l.google.com (20) Google, alt2.aspmx.l.google.com (30) Google, aspmx2.googlemail.com (40) Google, aspmx3.googlemail.com (50) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at adinplay.com is "v=spf1 include:_spf.google.com include:5128755.spf08.hubspotemail.net -all".
The DMARC text record at _dmarc.adinplay.com is "v=DMARC1; p=reject; pct=1; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1".
IPv4 address 198.202.211.1 answers for adinplay.com at resolver 1.1.1.1:53.
IPv6 address 2620:cb:2000::1 answers for adinplay.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 40. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 50. The host is recognised as Google.
A random label under adinplay.com also resolved, which means wildcard DNS is on.
Hosting and geo
adinplay.com is placed in San Francisco (South of Market), United States by the local geolocation database (db-ip).
| Address | 198.202.211.1 |
|---|---|
| Country | United States |
| City | San Francisco (South of Market) |
| Source | db-ip |
SSL/TLS
The certificate for adinplay.com is valid, with 88 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | adinplay.com |
| Valid from | 29 October 2026 |
| Valid until | 27 January 2027 |
| Days left | 88 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: adinplay.com.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Cloudflare · CDN
- Google Analytics · Analytics
- Google Font API · Font scripts
- Google Hosted Libraries · CDN
- Google Tag Manager · Tag managers
- HSTS · Security
- HTTP/3 · Miscellaneous
- jQuery · JavaScript libraries
- jsDelivr · CDN
Cloudflare is filed under CDN.
Google Analytics is filed under Analytics.
Google Font API is filed under Font scripts.
Google Hosted Libraries is filed under CDN.
Google Tag Manager is filed under Tag managers.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
jsDelivr is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 47 ms. The target title is 55 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 47 ms |
| Title length | 55 yes |
| Quoted title | "AdinPlay | Maximise Ad Revenue and Optimise Performance" |
| Meta description | "AdinPlay helps browser game publishers optimize ad performance and maximize revenue for your websites, apps and online games." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://adinplay.com |
| Language | en |
| Links | 41 |
| Images | 22 |
| 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 adinplay.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 | yes |
| CSP | yes |
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 15 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: rdap expires changed from 2026-12-04T10:24:27Z to 2027-12-04T10:24:27Z.
- October 2026: rdap updated changed from 2026-05-14T10:20:35Z to 2026-10-30T10:28:46Z.
- October 2026: geo city changed from empty to San Francisco (South of Market).
- October 2026: geo country changed from empty to United States.
Questions
Is adinplay.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 adinplay.com?
adinplay.com is placed in San Francisco (South of Market), United States.
When does adinplay.com expire?
adinplay.com expires on 4 December 2027 according to https://rdap.verisign.com/com/v1/domain/adinplay.com.
Who owns adinplay.com?
The registry did not return a person or a company for adinplay.com. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/adinplay.com at 2026-10-30T13:43:03Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:43:03Z
- TLS source tls:443 at 2026-10-30T13:43:03Z
- HTTP source https://adinplay.com/ at 2026-10-30T13:43:03Z
- Tech source wappalyzergo at 2026-10-30T13:43:03Z
- Geo source db-ip at 2026-10-30T13:43:03Z
- Safety source family DNS and local lists at 2026-10-30T13:43:03Z
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.