gmgard.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 88 days left11 years oldTranco #523828
85
gmgard.com was registered on 31 Mar 2015 via GoDaddy.com, LLC and the registry expiry is 31 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/gmgard.com.
gmgard.com publishes 2 nameservers. DNSSEC is signed.
gmgard.com has 3 IPv4 addresses (104.26.6.72, 104.26.7.72, 172.67.69.139) and 3 IPv6 addresses (2606:4700:20::681a:648, 2606:4700:20::681a:748, 2606:4700:20::ac43:458b). The geolocation database places 104.26.6.72 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Cloudflare Browser Insights, Google Analytics, HSTS, HTTP/3, Microsoft ASP.NET, cdnjs and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for gmgard.com in the checks that ran.
Domain · RDAP/WHOIS
gmgard.com was registered on 31 Mar 2015 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/gmgard.com.
| Registered | since 31 Mar 2015 |
|---|---|
| Created | 31 March 2015 |
| Updated | 31 March 2025 |
| Expires | 31 March 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | hera.ns.cloudflare.com, matt.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/gmgard.com |
gmgard.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
gmgard.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
gmgard.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.
gmgard.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver hera.ns.cloudflare.com is published for gmgard.com in the registration record from https://rdap.verisign.com/com/v1/domain/gmgard.com.
Nameserver matt.ns.cloudflare.com is published for gmgard.com in the registration record from https://rdap.verisign.com/com/v1/domain/gmgard.com.
DNS
gmgard.com has 6 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.6.72, 104.26.7.72, 172.67.69.139 |
|---|---|
| AAAA | 2606:4700:20::681a:648, 2606:4700:20::681a:748, 2606:4700:20::ac43:458b |
| NS | hera.ns.cloudflare.com, matt.ns.cloudflare.com |
| MX | gmgard-com.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at gmgard.com is "v=spf1 include:spf.protection.outlook.com -all".
IPv4 address 104.26.6.72 answers for gmgard.com at resolver 1.1.1.1:53.
IPv4 address 104.26.7.72 answers for gmgard.com at resolver 1.1.1.1:53.
IPv4 address 172.67.69.139 answers for gmgard.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:648 answers for gmgard.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:748 answers for gmgard.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:458b answers for gmgard.com at resolver 1.1.1.1:53.
Mail exchanger gmgard-com.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
gmgard.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.6.72 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for gmgard.com is valid, with 88 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | gmgard.com |
| Valid from | 29 October 2026 |
| Valid until | 27 January 2027 |
| Days left | 88 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.gmgard.com, gmgard.com.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- Google Analytics · Analytics
- HSTS · Security
- HTTP/3 · Miscellaneous
- Microsoft ASP.NET · Web frameworks
- cdnjs · CDN
- jQuery · JavaScript libraries
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Microsoft ASP.NET is filed under Web frameworks.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 1023 ms. The target title is 31 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 1023 ms |
| Title length | 31 yes |
| Quoted title | "GMgard - 紳士の庭 ♢绅士们的二次元资源分享交流平台♢" |
| Meta description | "gmgard.com♢紳士の庭♢ 绅士们的二次元资源分享交流平台" yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | zh-cn |
| Links | 172 |
| Images | 30 |
| 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 gmgard.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 10 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
First checked on 30 October 2026; changes will appear here.
Questions
Is gmgard.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 gmgard.com?
gmgard.com is placed in Toronto, Canada.
When does gmgard.com expire?
gmgard.com expires on 31 March 2027 according to https://rdap.verisign.com/com/v1/domain/gmgard.com.
Who owns gmgard.com?
The registry did not return a person or a company for gmgard.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/gmgard.com at 2026-10-30T13:56:24Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:56:24Z
- TLS source tls:443 at 2026-10-30T13:56:24Z
- HTTP source https://gmgard.com/ at 2026-10-30T13:56:24Z
- Tech source wappalyzergo at 2026-10-30T13:56:24Z
- Geo source db-ip at 2026-10-30T13:56:24Z
- Safety source family DNS and local lists at 2026-10-30T13:56:24Z
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.