datingcdn.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 78 days left10 years old
70
datingcdn.com was registered on 1 Nov 2016 via Internet Domain Service BS Corp and the registry expiry is 1 Nov 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/datingcdn.com.
datingcdn.com publishes 6 nameservers. DNSSEC is not signed.
datingcdn.com has 1 IPv4 address (83.126.45.206). The geolocation database places 83.126.45.206 in Amsterdam, The Netherlands.
The TLS certificate from YR1 is valid and has 78 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named HSTS, Nginx and Ubuntu. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for datingcdn.com in the checks that ran.
Domain · RDAP/WHOIS
datingcdn.com was registered on 1 Nov 2016 via Internet Domain Service BS Corp. The registry returned 1 status value and 6 nameservers from https://rdap.verisign.com/com/v1/domain/datingcdn.com.
| Registered | since 1 Nov 2016 |
|---|---|
| Created | 1 November 2016 |
| Updated | 30 October 2026 |
| Expires | 1 November 2027 |
| Registrar | Internet Domain Service BS Corp |
| Status | client transfer prohibited |
| Nameservers | ns11.constellix.com, ns21.constellix.com, ns31.constellix.com, ns41.constellix.net, ns51.constellix.net, ns61.constellix.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/datingcdn.com |
datingcdn.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 ns11.constellix.com is published for datingcdn.com in the registration record from https://rdap.verisign.com/com/v1/domain/datingcdn.com.
Nameserver ns21.constellix.com is published for datingcdn.com in the registration record from https://rdap.verisign.com/com/v1/domain/datingcdn.com.
Nameserver ns31.constellix.com is published for datingcdn.com in the registration record from https://rdap.verisign.com/com/v1/domain/datingcdn.com.
Nameserver ns41.constellix.net is published for datingcdn.com in the registration record from https://rdap.verisign.com/com/v1/domain/datingcdn.com.
Nameserver ns51.constellix.net is published for datingcdn.com in the registration record from https://rdap.verisign.com/com/v1/domain/datingcdn.com.
Nameserver ns61.constellix.net is published for datingcdn.com in the registration record from https://rdap.verisign.com/com/v1/domain/datingcdn.com.
DNS
datingcdn.com has 1 address record, 0 mail exchangers and 6 nameservers, measured at 1.1.1.1:53.
| A | 83.126.45.206 |
|---|---|
| AAAA | — |
| NS | ns11.constellix.com, ns21.constellix.com, ns31.constellix.com, ns41.constellix.net, ns51.constellix.net, ns61.constellix.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 83.126.45.206 answers for datingcdn.com at resolver 1.1.1.1:53.
Hosting and geo
datingcdn.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 83.126.45.206 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for datingcdn.com is valid, with 78 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | datingcdn.com |
| Valid from | 20 October 2026 |
| Valid until | 18 January 2027 |
| Days left | 78 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: datingcdn.com, www.datingcdn.com.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- HSTS · Security
- Nginx · Web servers, Reverse proxies
- Ubuntu · Operating systems
HSTS is filed under Security.
Nginx is filed under Web servers, Reverse proxies.
Ubuntu is filed under Operating systems.
On-page checks
The homepage returned HTTP 200 in 24 ms. The target title is 10 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 24 ms |
| Title length | 10 yes |
| Quoted title | "Dating CDN" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 datingcdn.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 0 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: dns a changed from 185.152.87.70 to 83.126.45.206.
- October 2026: tls protocol changed from TLS 1.2 to TLS 1.3.
- October 2026: geo city changed from empty to Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is datingcdn.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 datingcdn.com?
datingcdn.com is placed in Amsterdam, The Netherlands.
When does datingcdn.com expire?
datingcdn.com expires on 1 November 2027 according to https://rdap.verisign.com/com/v1/domain/datingcdn.com.
Who owns datingcdn.com?
The registry did not return a person or a company for datingcdn.com. RDAP often redacts the registrant. The registrar on file is Internet Domain Service BS Corp.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/datingcdn.com at 2026-10-30T13:51:18Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:51:18Z
- TLS source tls:443 at 2026-10-30T13:51:18Z
- HTTP source https://datingcdn.com/ at 2026-10-30T13:51:18Z
- Tech source wappalyzergo at 2026-10-30T13:51:18Z
- Geo source db-ip at 2026-10-30T13:51:18Z
- Safety source family DNS and local lists at 2026-10-30T13:51:18Z
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.