1r1g.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 83 days left7 years oldTranco #342315
75
1r1g.com was registered on 30 Mar 2019 via DNSPod, Inc. and the registry expiry is 30 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/1r1g.com.
1r1g.com publishes 2 nameservers. DNSSEC is not signed.
1r1g.com has 1 IPv4 address (43.138.133.127). The geolocation database places 43.138.133.127 in Guangzhou, China.
The TLS certificate from YR2 is valid and has 83 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Bootstrap, Google AdSense, Google Analytics, Nginx, Popper and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for 1r1g.com in the checks that ran.
Domain · RDAP/WHOIS
1r1g.com was registered on 30 Mar 2019 via DNSPod, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/1r1g.com.
| Registered | since 30 Mar 2019 |
|---|---|
| Created | 30 March 2019 |
| Updated | 29 January 2026 |
| Expires | 30 March 2027 |
| Registrar | DNSPod, Inc. |
| Status | active |
| Nameservers | f1g1ns1.dnspod.net, f1g1ns2.dnspod.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/1r1g.com |
Nameserver f1g1ns1.dnspod.net is published for 1r1g.com in the registration record from https://rdap.verisign.com/com/v1/domain/1r1g.com.
Nameserver f1g1ns2.dnspod.net is published for 1r1g.com in the registration record from https://rdap.verisign.com/com/v1/domain/1r1g.com.
DNS
1r1g.com has 1 address record, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 43.138.133.127 |
|---|---|
| AAAA | — |
| NS | f1g1ns1.dnspod.net, f1g1ns2.dnspod.net |
| MX | mxbiz1.qq.com (5), mxbiz2.qq.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at 1r1g.com is "v=spf1 include:spf.mail.qq.com ~all".
IPv4 address 43.138.133.127 answers for 1r1g.com at resolver 1.1.1.1:53.
Mail exchanger mxbiz1.qq.com has preference 5.
Mail exchanger mxbiz2.qq.com has preference 10.
A random label under 1r1g.com also resolved, which means wildcard DNS is on.
Hosting and geo
1r1g.com is placed in Guangzhou, China by the local geolocation database (db-ip).
| Address | 43.138.133.127 |
|---|---|
| Country | China |
| City | Guangzhou |
| Source | db-ip |
SSL/TLS
The certificate for 1r1g.com is valid, with 83 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | 1r1g.com |
| Valid from | 24 October 2026 |
| Valid until | 22 January 2027 |
| Days left | 83 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.1r1g.com, 1r1g.com.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Google AdSense · Advertising
- Google Analytics · Analytics
- Nginx · Web servers, Reverse proxies
- Popper · Miscellaneous
- jQuery · JavaScript libraries
Bootstrap is filed under UI frameworks.
Google AdSense is filed under Advertising.
Google Analytics is filed under Analytics.
Nginx is filed under Web servers, Reverse proxies.
Popper is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 194 ms. The target title is 19 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 194 ms |
| Title length | 19 yes |
| Quoted title | "问题列表 - 第1页 | 个人经验分享" |
| Meta description | "解决问题列表部分：《为什么处理排序数组比处理未排序数组更快？》《'git pull'和'git fetch'有什么区别？》《C++中的" - >"运算符是什么？》" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | zh-cn |
| Links | 125 |
| Images | 0 |
| 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 1r1g.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 | 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 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 Guangzhou.
- October 2026: geo country changed from empty to China.
Questions
Is 1r1g.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 1r1g.com?
1r1g.com is placed in Guangzhou, China.
When does 1r1g.com expire?
1r1g.com expires on 30 March 2027 according to https://rdap.verisign.com/com/v1/domain/1r1g.com.
Who owns 1r1g.com?
The registry did not return a person or a company for 1r1g.com. RDAP often redacts the registrant. The registrar on file is DNSPod, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/1r1g.com at 2026-10-30T13:41:04Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:41:04Z
- TLS source tls:443 at 2026-10-30T13:41:04Z
- HTTP source https://1r1g.com/ at 2026-10-30T13:41:04Z
- Tech source wappalyzergo at 2026-10-30T13:41:04Z
- Geo source db-ip at 2026-10-30T13:41:04Z
- Safety source family DNS and local lists at 2026-10-30T13:41:04Z
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.