moongiant.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 57 days left19 years oldTranco #72460
80
moongiant.com was registered on 2 Dec 2006 via GoDaddy.com, LLC and the registry expiry is 2 Dec 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/moongiant.com.
moongiant.com publishes 2 nameservers. DNSSEC is signed.
moongiant.com has 3 IPv4 addresses (104.26.0.59, 104.26.1.59, 172.67.73.149) and 3 IPv6 addresses (2606:4700:20::681a:13b, 2606:4700:20::681a:3b, 2606:4700:20::ac43:4995). The geolocation database places 104.26.0.59 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 57 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Cloudflare Browser Insights, Google AdSense, Google Analytics, Google Hosted Libraries, Moment.js, cdnjs and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for moongiant.com in the checks that ran.
Domain · RDAP/WHOIS
moongiant.com was registered on 2 Dec 2006 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/moongiant.com.
| Registered | since 2 Dec 2006 |
|---|---|
| Created | 2 December 2006 |
| Updated | 15 July 2026 |
| Expires | 2 December 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | dax.ns.cloudflare.com, sierra.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/moongiant.com |
moongiant.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.
moongiant.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.
moongiant.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.
moongiant.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 dax.ns.cloudflare.com is published for moongiant.com in the registration record from https://rdap.verisign.com/com/v1/domain/moongiant.com.
Nameserver sierra.ns.cloudflare.com is published for moongiant.com in the registration record from https://rdap.verisign.com/com/v1/domain/moongiant.com.
DNS
moongiant.com has 6 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.0.59, 104.26.1.59, 172.67.73.149 |
|---|---|
| AAAA | 2606:4700:20::681a:13b, 2606:4700:20::681a:3b, 2606:4700:20::ac43:4995 |
| NS | dax.ns.cloudflare.com, sierra.ns.cloudflare.com |
| MX | mailwash62.pair.com (50) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at moongiant.com is "v=spf1 include:servers.mcsv.net ?all".
The DMARC text record at _dmarc.moongiant.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 104.26.0.59 answers for moongiant.com at resolver 1.1.1.1:53.
IPv4 address 104.26.1.59 answers for moongiant.com at resolver 1.1.1.1:53.
IPv4 address 172.67.73.149 answers for moongiant.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:13b answers for moongiant.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:3b answers for moongiant.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4995 answers for moongiant.com at resolver 1.1.1.1:53.
Mail exchanger mailwash62.pair.com has preference 50.
Hosting and geo
moongiant.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.0.59 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for moongiant.com is valid, with 57 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | moongiant.com |
| Valid from | 29 September 2026 |
| Valid until | 28 December 2026 |
| Days left | 57 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.moongiant.com, moongiant.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 AdSense · Advertising
- Google Analytics · Analytics
- Google Hosted Libraries · CDN
- Moment.js · JavaScript libraries
- 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 AdSense is filed under Advertising.
Google Analytics is filed under Analytics.
Google Hosted Libraries is filed under CDN.
Moment.js is filed under JavaScript libraries.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 54 ms. The target title is 26 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 54 ms |
| Title length | 26 yes |
| Quoted title | "Moongiant > Next Full Moon" |
| Meta description | "The Next Full Moon will be on November 24, 2026 9:53am EST. Visit Moongiant to track the Moon Phase daily, monthly, yearly and always know when the next Full Moon is coming." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://www.moongiant.com |
| Language | en |
| Links | 20 |
| Images | 27 |
| 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 moongiant.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 15 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
First checked on 30 October 2026; changes will appear here.
Questions
Is moongiant.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 moongiant.com?
moongiant.com is placed in Toronto, Canada.
When does moongiant.com expire?
moongiant.com expires on 2 December 2028 according to https://rdap.verisign.com/com/v1/domain/moongiant.com.
Who owns moongiant.com?
The registry did not return a person or a company for moongiant.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/moongiant.com at 2026-10-30T14:04:43Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:04:43Z
- TLS source tls:443 at 2026-10-30T14:04:43Z
- HTTP source https://moongiant.com/ at 2026-10-30T14:04:43Z
- Tech source wappalyzergo at 2026-10-30T14:04:43Z
- Geo source db-ip at 2026-10-30T14:04:43Z
- Safety source family DNS and local lists at 2026-10-30T14:04:43Z
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.