rusdate.us
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 89 days left14 years oldTranco #712628
65
rusdate.us was registered on 6 Jan 2012 via Domain.com, LLC and the registry expiry is 5 Jan 2027. WHOIS data came from a WHOIS query because RDAP is not published for this TLD.
rusdate.us publishes 4 nameservers. DNSSEC is not signed.
rusdate.us has 2 IPv4 addresses (34.246.248.242, 52.214.204.193) and 2 IPv6 addresses (2a05:d018:17e1:2a00:2423:bb31:ff75:96f4, 2a05:d018:17e1:2a01:1818:3018:9e1d:9549). The geolocation database places 34.246.248.242 in Dublin, Ireland.
The TLS certificate from Amazon RSA 2048 M01 is valid and has 89 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Google AdSense, Google Sign-in, Google Tag Manager, Nginx, Slick, jQuery, jQuery Migrate and jQuery UI. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for rusdate.us in the checks that ran.
Domain · RDAP/WHOIS
rusdate.us was registered on 6 Jan 2012 via Domain.com, LLC. The registry returned 1 status value and 3 nameservers from whois://whois.nic.us.
| Registered | since 6 Jan 2012 |
|---|---|
| Created | 6 January 2012 |
| Updated | 21 December 2025 |
| Expires | 5 January 2027 |
| Registrar | Domain.com, LLC |
| Status | ok |
| Nameservers | ns-1325.awsdns-37.org, ns-1756.awsdns-27.co.uk, ns-618.awsdns-13.net |
| DNSSEC | unknown |
| Source | whois://whois.nic.us |
RDAP is not available for .us
rusdate.us carries the status "ok". The status ok means no other EPP status is set. It is not a safety verdict.
Nameserver ns-1325.awsdns-37.org is published for rusdate.us in the registration record from whois://whois.nic.us.
Nameserver ns-1756.awsdns-27.co.uk is published for rusdate.us in the registration record from whois://whois.nic.us.
Nameserver ns-618.awsdns-13.net is published for rusdate.us in the registration record from whois://whois.nic.us.
DNS
rusdate.us has 4 address records, 7 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 34.246.248.242, 52.214.204.193 |
|---|---|
| AAAA | 2a05:d018:17e1:2a00:2423:bb31:ff75:96f4, 2a05:d018:17e1:2a01:1818:3018:9e1d:9549 |
| NS | ns-1325.awsdns-37.org, ns-1756.awsdns-27.co.uk, ns-368.awsdns-46.com, ns-618.awsdns-13.net |
| MX | aspmx.l.google.com (0) Google, alt1.aspmx.l.google.com (10) Google, alt2.aspmx.l.google.com (10) Google, aspmx2.googlemail.com (20) Google, aspmx3.googlemail.com (20) Google, aspmx4.googlemail.com (20) Google, aspmx5.googlemail.com (20) Google |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 34.246.248.242 answers for rusdate.us at resolver 1.1.1.1:53.
IPv4 address 52.214.204.193 answers for rusdate.us at resolver 1.1.1.1:53.
IPv6 address 2a05:d018:17e1:2a00:2423:bb31:ff75:96f4 answers for rusdate.us at resolver 1.1.1.1:53.
IPv6 address 2a05:d018:17e1:2a01:1818:3018:9e1d:9549 answers for rusdate.us at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 0. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 20. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 20. The host is recognised as Google.
Mail exchanger aspmx4.googlemail.com has preference 20. The host is recognised as Google.
Mail exchanger aspmx5.googlemail.com has preference 20. The host is recognised as Google.
Hosting and geo
rusdate.us is placed in Dublin, Ireland by the local geolocation database (db-ip).
| Address | 34.246.248.242 |
|---|---|
| Country | Ireland |
| City | Dublin |
| Source | db-ip |
SSL/TLS
The certificate for rusdate.us is valid, with 89 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M01 |
|---|---|
| Subject | rusdate.us |
| Valid from | 30 December 2025 |
| Valid until | 28 January 2027 |
| Days left | 89 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.rusdate.us, rusdate.us.
Tech stack
Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.
- Google AdSense · Advertising
- Google Sign-in · Authentication
- Google Tag Manager · Tag managers
- Nginx · Web servers, Reverse proxies
- Slick · JavaScript libraries
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
- jQuery UI · JavaScript libraries
Google AdSense is filed under Advertising.
Google Sign-in is filed under Authentication.
Google Tag Manager is filed under Tag managers.
Nginx is filed under Web servers, Reverse proxies.
Slick is filed under JavaScript libraries.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
jQuery UI is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 122 ms. The target title is 83 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 122 ms |
| Title length | 83 no |
| Quoted title | "❤ Знакомства в Америке для русскоязычных | Сайт онлайн знакомств в США - RusDate.us" |
| Meta description | "Сайт знакомств на русском в США RusDate.us собрал огромную базу анкет мужчин и женщин, которые ищут онлайн знакомства в Америке. Присоединяйтесь и найдите себе пару прямо сейчас." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://rusdate.us |
| Language | — |
| Links | 155 |
| Images | 94 |
| 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 rusdate.us 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 0 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 Dublin.
- October 2026: geo country changed from empty to Ireland.
Questions
Is rusdate.us 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 rusdate.us?
rusdate.us is placed in Dublin, Ireland.
When does rusdate.us expire?
rusdate.us expires on 5 January 2027 according to whois://whois.nic.us.
Who owns rusdate.us?
The registry did not return a person or a company for rusdate.us. RDAP often redacts the registrant. The registrar on file is Domain.com, LLC.
Sources
- RDAP source whois://whois.nic.us at 2026-10-30T16:31:08Z
- DNS source 1.1.1.1:53 at 2026-10-30T16:31:08Z
- TLS source tls:443 at 2026-10-30T16:31:08Z
- HTTP source https://rusdate.us/ at 2026-10-30T16:31:08Z
- Tech source wappalyzergo at 2026-10-30T16:31:08Z
- Geo source db-ip at 2026-10-30T16:31:08Z
- Safety source family DNS and local lists at 2026-10-30T16:31:08Z
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.