g2fame.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 57 days left4 years oldTranco #115011
60
g2fame.com was registered on 11 May 2022 via Tucows Domains Inc. and the registry expiry is 11 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/g2fame.com.
g2fame.com publishes 2 nameservers. DNSSEC is not signed.
g2fame.com has 3 IPv4 addresses (104.26.14.127, 104.26.15.127, 172.67.75.124). The geolocation database places 104.26.14.127 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 Cloudflare. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
g2fame.com was registered on 11 May 2022 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/g2fame.com.
| Registered | since 11 May 2022 |
|---|---|
| Created | 11 May 2022 |
| Updated | 12 April 2026 |
| Expires | 11 May 2027 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | etta.ns.cloudflare.com, vick.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/g2fame.com |
g2fame.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.
g2fame.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 etta.ns.cloudflare.com is published for g2fame.com in the registration record from https://rdap.verisign.com/com/v1/domain/g2fame.com.
Nameserver vick.ns.cloudflare.com is published for g2fame.com in the registration record from https://rdap.verisign.com/com/v1/domain/g2fame.com.
DNS
g2fame.com has 3 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.14.127, 104.26.15.127, 172.67.75.124 |
|---|---|
| AAAA | — |
| NS | etta.ns.cloudflare.com, vick.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.26.14.127 answers for g2fame.com at resolver 1.1.1.1:53.
IPv4 address 104.26.15.127 answers for g2fame.com at resolver 1.1.1.1:53.
IPv4 address 172.67.75.124 answers for g2fame.com at resolver 1.1.1.1:53.
Hosting and geo
g2fame.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.14.127 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for g2fame.com is valid, with 57 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | g2fame.com |
| Valid from | 28 September 2026 |
| Valid until | 27 December 2026 |
| Days left | 57 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.g2fame.com, g2fame.com.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- Cloudflare · CDN
Cloudflare is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 25 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 25 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 g2fame.com 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 | yes |
Cloudflare family DNS returned a block for g2fame.com. 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.
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 10 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.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is g2fame.com safe?
Cloudflare family DNS returned a block for g2fame.com. That resolver covers adult and malware names.
Who hosts g2fame.com?
g2fame.com is placed in Toronto, Canada.
When does g2fame.com expire?
g2fame.com expires on 11 May 2027 according to https://rdap.verisign.com/com/v1/domain/g2fame.com.
Who owns g2fame.com?
The registry did not return a person or a company for g2fame.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/g2fame.com at 2026-10-30T13:55:40Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:55:40Z
- TLS source tls:443 at 2026-10-30T13:55:40Z
- HTTP source https://g2fame.com/ at 2026-10-30T13:55:40Z
- Tech source wappalyzergo at 2026-10-30T13:55:40Z
- Geo source db-ip at 2026-10-30T13:55:40Z
- Safety source family DNS and local lists at 2026-10-30T13:55:40Z
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.