agarprivateservers.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 87 days left8 years old
70
agarprivateservers.org was registered on 1 Feb 2018 via Automattic Inc. and the registry expiry is 1 Feb 2028. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org.
agarprivateservers.org publishes 4 nameservers. DNSSEC is not signed.
agarprivateservers.org has 1 IPv4 address (89.252.180.243) and 1 IPv6 address (2a06:41c0:1:30::315). The geolocation database places 89.252.180.243 in Ataşehir, Turkey.
The TLS certificate from YR2 is valid and has 87 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Google Publisher Tag, Google Web Server, HTTP/3, LiteSpeed, LiteSpeed Cache, Litespeed Cache, jQuery and jsDelivr. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for agarprivateservers.org in the checks that ran.
Domain · RDAP/WHOIS
agarprivateservers.org was registered on 1 Feb 2018 via Automattic Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org.
| Registered | since 1 Feb 2018 |
|---|---|
| Created | 1 February 2018 |
| Updated | 4 September 2026 |
| Expires | 1 February 2028 |
| Registrar | Automattic Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.guzelhosting.com, ns11.guzelhosting.com, ns12.guzelhosting.com, ns2.guzelhosting.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org |
agarprivateservers.org 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.guzelhosting.com is published for agarprivateservers.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org.
Nameserver ns11.guzelhosting.com is published for agarprivateservers.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org.
Nameserver ns12.guzelhosting.com is published for agarprivateservers.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org.
Nameserver ns2.guzelhosting.com is published for agarprivateservers.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org.
DNS
agarprivateservers.org has 2 address records, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 89.252.180.243 |
|---|---|
| AAAA | 2a06:41c0:1:30::315 |
| NS | ns1.guzelhosting.com, ns11.guzelhosting.com, ns12.guzelhosting.com, ns2.guzelhosting.com |
| MX | agarprivateservers.org (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at agarprivateservers.org is "v=spf1 a mx include:relay.guzelhosting.com ~all".
IPv4 address 89.252.180.243 answers for agarprivateservers.org at resolver 1.1.1.1:53.
IPv6 address 2a06:41c0:1:30::315 answers for agarprivateservers.org at resolver 1.1.1.1:53.
Mail exchanger agarprivateservers.org has preference 0.
Hosting and geo
agarprivateservers.org is placed in Ataşehir, Turkey by the local geolocation database (db-ip).
| Address | 89.252.180.243 |
|---|---|
| Country | Turkey |
| City | Ataşehir |
| Source | db-ip |
SSL/TLS
The certificate for agarprivateservers.org is valid, with 87 days left and 3 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | agarprivateservers.org |
| Valid from | 28 October 2026 |
| Valid until | 26 January 2027 |
| Days left | 87 |
| SAN count | 3 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: agarprivateservers.org, mail.agarprivateservers.org, www.agarprivateservers.org.
Tech stack
Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.
- Google Publisher Tag · Advertising
- Google Web Server · Web servers
- HTTP/3 · Miscellaneous
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- jQuery · JavaScript libraries
- jsDelivr · CDN
Google Publisher Tag is filed under Advertising.
Google Web Server is filed under Web servers.
HTTP/3 is filed under Miscellaneous.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
jQuery is filed under JavaScript libraries.
jsDelivr is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 418 ms. The target title is 36 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 418 ms |
| Title length | 36 yes |
| Quoted title | "Agario Private Server | Agar.io Game" |
| Meta description | "Agario Private Server, Agar Private Server, Agario Private Servers, Agar.io Private Server" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | — |
| Language | en |
| Links | 18 |
| Images | 9 |
| 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 agarprivateservers.org 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 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 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 Ataşehir.
- October 2026: geo country changed from empty to Turkey.
Questions
Is agarprivateservers.org 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 agarprivateservers.org?
agarprivateservers.org is placed in Ataşehir, Turkey.
When does agarprivateservers.org expire?
agarprivateservers.org expires on 1 February 2028 according to https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org.
Who owns agarprivateservers.org?
The registry did not return a person or a company for agarprivateservers.org. RDAP often redacts the registrant. The registrar on file is Automattic Inc..
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/agarprivateservers.org at 2026-10-30T15:00:58Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:00:58Z
- TLS source tls:443 at 2026-10-30T15:00:58Z
- HTTP source https://agarprivateservers.org/ at 2026-10-30T15:00:58Z
- Tech source wappalyzergo at 2026-10-30T15:00:58Z
- Geo source db-ip at 2026-10-30T15:00:58Z
- Safety source family DNS and local lists at 2026-10-30T15:00:58Z
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.