gamehayvl.io
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe2 years old
35
gamehayvl.io was registered on 16 Oct 2024 via Spaceship, Inc. and the registry expiry is 16 Oct 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/gamehayvl.io.
gamehayvl.io publishes 2 nameservers. DNSSEC is not signed.
gamehayvl.io has 1 IPv4 address (162.4.84.215). The geolocation database places 162.4.84.215 in Los Angeles, United States.
No safety warning was recorded for gamehayvl.io in the checks that ran.
Domain · RDAP/WHOIS
gamehayvl.io was registered on 16 Oct 2024 via Spaceship, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/gamehayvl.io.
| Registered | since 16 Oct 2024 |
|---|---|
| Created | 16 October 2024 |
| Updated | 12 August 2026 |
| Expires | 16 October 2027 |
| Registrar | Spaceship, Inc. |
| Status | client transfer prohibited |
| Nameservers | a.2ns.net, b.2ns.net |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/gamehayvl.io |
gamehayvl.io 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.
Nameserver a.2ns.net is published for gamehayvl.io in the registration record from https://rdap.identitydigital.services/rdap/domain/gamehayvl.io.
Nameserver b.2ns.net is published for gamehayvl.io in the registration record from https://rdap.identitydigital.services/rdap/domain/gamehayvl.io.
DNS
gamehayvl.io has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 162.4.84.215 |
|---|---|
| AAAA | — |
| NS | ns4.dnsauthority.com, ns5.dnsauthority.com |
| MX | mail.hope-mail.com (1) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at gamehayvl.io is "v=spf1 ip6:fd18:d113:9bed::/48 -all".
IPv4 address 162.4.84.215 answers for gamehayvl.io at resolver 1.1.1.1:53.
Mail exchanger mail.hope-mail.com has preference 1.
A random label under gamehayvl.io also resolved, which means wildcard DNS is on.
Hosting and geo
gamehayvl.io is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 162.4.84.215 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for gamehayvl.io on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup gamehayvl.io: i/o timeout
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://gamehayvl.io/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for gamehayvl.io 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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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 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
- October 2026: rdap created changed from 2024-10-16T15:15:07Z to 2024-10-16T15:15:07.84Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-10-16T15:15:07Z to 2027-10-16T15:15:07.84Z.
- October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
- October 2026: rdap updated changed from 2026-08-12T07:44:44Z to 2026-08-12T07:44:44.95Z.
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
- October 2026: safety family changed from unknown to clear.
Questions
Is gamehayvl.io 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 gamehayvl.io?
gamehayvl.io is placed in Los Angeles, United States.
When does gamehayvl.io expire?
gamehayvl.io expires on 16 October 2027 according to https://rdap.identitydigital.services/rdap/domain/gamehayvl.io.
Who owns gamehayvl.io?
The registry did not return a person or a company for gamehayvl.io. RDAP often redacts the registrant. The registrar on file is Spaceship, Inc..
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/gamehayvl.io at 2026-10-30T14:34:02Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:34:02Z
- TLS source tls:443 at 2026-10-30T14:34:02Z
- HTTP source https://gamehayvl.io/ at 2026-10-30T14:34:02Z
- Tech source not available at 2026-10-30T14:34:02Z
- Geo source db-ip at 2026-10-30T14:34:02Z
- Safety source family DNS and local lists at 2026-10-30T14:34:02Z
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.