ansedo.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 61 days left8 years oldTranco #576058
80
ansedo.com was registered on 6 Jan 2018 via Regtime Ltd. and the registry expiry is 6 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/ansedo.com.
ansedo.com publishes 2 nameservers. DNSSEC is not signed.
ansedo.com has 1 IPv4 address (111.88.126.7). The geolocation database places 111.88.126.7 in Moscow, Russia.
The TLS certificate from YE2 is valid and has 61 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named HSTS and Nginx. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for ansedo.com in the checks that ran.
Domain · RDAP/WHOIS
ansedo.com was registered on 6 Jan 2018 via Regtime Ltd.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/ansedo.com.
| Registered | since 6 Jan 2018 |
|---|---|
| Created | 6 January 2018 |
| Updated | 22 December 2025 |
| Expires | 6 January 2027 |
| Registrar | Regtime Ltd. |
| Status | active |
| Nameservers | ns1.ihc.ru, ns2.ihc.ru |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/ansedo.com |
Nameserver ns1.ihc.ru is published for ansedo.com in the registration record from https://rdap.verisign.com/com/v1/domain/ansedo.com.
Nameserver ns2.ihc.ru is published for ansedo.com in the registration record from https://rdap.verisign.com/com/v1/domain/ansedo.com.
DNS
ansedo.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 111.88.126.7 |
|---|---|
| AAAA | — |
| NS | ns1.ihc.ru, ns2.ihc.ru |
| MX | mx.ansedo.com (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at ansedo.com is "v=spf1 a mx include:spf.mail.selcloud.ru ~all".
The DMARC text record at _dmarc.ansedo.com is "v=DMARC1; p=none;".
IPv4 address 111.88.126.7 answers for ansedo.com at resolver 1.1.1.1:53.
Mail exchanger mx.ansedo.com has preference 10.
Hosting and geo
ansedo.com is placed in Moscow, Russia by the local geolocation database (db-ip).
| Address | 111.88.126.7 |
|---|---|
| Country | Russia |
| City | Moscow |
| Source | db-ip |
SSL/TLS
The certificate for ansedo.com is valid, with 61 days left and 6 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | ansedo.com |
| Valid from | 2 October 2026 |
| Valid until | 31 December 2026 |
| Days left | 61 |
| SAN count | 6 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: ansedo.com, ansedo.ru, mail.ansedo.com, staging.ansedo.com, www.ansedo.com, www.ansedo.ru.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- HSTS · Security
- Nginx · Web servers, Reverse proxies
HSTS is filed under Security.
Nginx is filed under Web servers, Reverse proxies.
On-page checks
The homepage returned HTTP 200 in 48 ms. The target title is 36 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 48 ms |
| Title length | 36 yes |
| Quoted title | "Find teams and players on ansedo.com" |
| Meta description | "Find teammates to play with or build a team." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://ansedo.com/en |
| Language | en |
| Links | 83 |
| Images | 66 |
| 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 ansedo.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 | 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 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
- October 2026: geo city changed from empty to Moscow.
- October 2026: geo country changed from empty to Russia.
Questions
Is ansedo.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 ansedo.com?
ansedo.com is placed in Moscow, Russia.
When does ansedo.com expire?
ansedo.com expires on 6 January 2027 according to https://rdap.verisign.com/com/v1/domain/ansedo.com.
Who owns ansedo.com?
The registry did not return a person or a company for ansedo.com. RDAP often redacts the registrant. The registrar on file is Regtime Ltd..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/ansedo.com at 2026-10-30T13:44:37Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:44:37Z
- TLS source tls:443 at 2026-10-30T13:44:37Z
- HTTP source https://ansedo.com/ at 2026-10-30T13:44:37Z
- Tech source wappalyzergo at 2026-10-30T13:44:37Z
- Geo source db-ip at 2026-10-30T13:44:37Z
- Safety source family DNS and local lists at 2026-10-30T13:44:37Z
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.