tongying.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
35
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
35
tongying.cc was registered on 7 Nov 2024 via Tradewinds Names, LLC and the registry expiry is 7 Nov 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/tongying.cc.
tongying.cc publishes 2 nameservers. DNSSEC is not signed.
tongying.cc has 1 IPv4 address (77.247.179.84). The geolocation database places 77.247.179.84 in Amsterdam, The Netherlands.
The TLS certificate from YR2 is valid and has 24 days left (TLS 1.3).
tongying.cc was registered on 7 Nov 2024 via Tradewinds Names, LLC. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/tongying.cc.
| Registered | since 7 Nov 2024 |
|---|---|
| Created | 7 November 2024 |
| Updated | 29 October 2026 |
| Expires | 7 November 2027 |
| Registrar | Tradewinds Names, LLC |
| Status | active |
| Nameservers | ns1.badgerdns.com, ns2.badgerdns.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/tongying.cc |
Nameserver ns1.badgerdns.com is published for tongying.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/tongying.cc.
Nameserver ns2.badgerdns.com is published for tongying.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/tongying.cc.
tongying.cc has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 77.247.179.84 |
|---|---|
| AAAA | — |
| NS | ns1.badgerdns.com, ns2.badgerdns.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 77.247.179.84 answers for tongying.cc at resolver 1.1.1.1:53.
A random label under tongying.cc also resolved, which means wildcard DNS is on.
tongying.cc is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 77.247.179.84 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
The certificate for tongying.cc is valid, with 24 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | tongying.cc |
| Valid from | 27 August 2026 |
| Valid until | 25 November 2026 |
| Days left | 24 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.tongying.cc, tongying.cc.
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Head "http://surveymrs.com": read tcp 10.0.0.3:47068->208.91.196.145:80: read: connection reset by peer
Family DNS for tongying.cc is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for tongying.cc. That resolver covers adult and malware names.
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Availability 10 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 0 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.
Cloudflare family DNS returned a block for tongying.cc. That resolver covers adult and malware names.
tongying.cc is placed in Amsterdam, The Netherlands.
tongying.cc expires on 7 November 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/tongying.cc.
The registry did not return a person or a company for tongying.cc. RDAP often redacts the registrant. The registrar on file is Tradewinds Names, LLC.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.