lostarksteam.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

HTTP 429SafeSSL: 38 days leftUnder 1 year old

One re-check per domain each UTC day.

47

lostarksteam.com was registered on 18 Dec 2025 via Gname 363 Inc and the registry expiry is 18 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/lostarksteam.com.

lostarksteam.com publishes 2 nameservers. DNSSEC is not signed.

lostarksteam.com has 1 IPv4 address (76.76.21.21). The geolocation database places 76.76.21.21 in Walnut (Valle Lindo), United States.

The TLS certificate from YR1 is valid and has 38 days left (TLS 1.3).

Tech detection named Vercel. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for lostarksteam.com in the checks that ran.

Domain · RDAP/WHOIS

lostarksteam.com was registered on 18 Dec 2025 via Gname 363 Inc. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/lostarksteam.com.

Registeredsince 18 Dec 2025
Created18 December 2025
Updated9 July 2026
Expires18 December 2026
RegistrarGname 363 Inc
Statusclient transfer prohibited
Nameserversa8.share-dns.com, b8.share-dns.net
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/lostarksteam.com

lostarksteam.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.

Nameserver a8.share-dns.com is published for lostarksteam.com in the registration record from https://rdap.verisign.com/com/v1/domain/lostarksteam.com.

Nameserver b8.share-dns.net is published for lostarksteam.com in the registration record from https://rdap.verisign.com/com/v1/domain/lostarksteam.com.

DNS

lostarksteam.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A76.76.21.21
AAAA—
NSa.share-dns.com, b.share-dns.net
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 76.76.21.21 answers for lostarksteam.com at resolver 1.1.1.1:53.

Hosting and geo

lostarksteam.com is placed in Walnut (Valle Lindo), United States by the local geolocation database (db-ip).

Address76.76.21.21
CountryUnited States
CityWalnut (Valle Lindo)
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for lostarksteam.com is valid, with 38 days left and 1 subject alternative name. Source: tls:443.

IssuerYR1
Subjectlostarksteam.com
Valid from12 September 2026
Valid until11 December 2026
Days left38
SAN count1
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: lostarksteam.com.

Tech stack

Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.

  • Vercel · PaaS

Vercel is filed under PaaS.

On-page checks

The homepage returned HTTP 429 in 11 ms. The target title is 26 characters and the page has 0 H1 headings.

Status429
TTFB11 ms
Title length26 yes
Quoted title"Vercel Security Checkpoint"
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Languageen
Links1
Images0
Faviconyes

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 lostarksteam.com is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

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 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 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 2 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: geo city changed from empty to Walnut (Valle Lindo).
  • October 2026: geo country changed from empty to United States.

Questions

Is lostarksteam.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 lostarksteam.com?

lostarksteam.com is placed in Walnut (Valle Lindo), United States.

When does lostarksteam.com expire?

lostarksteam.com expires on 18 December 2026 according to https://rdap.verisign.com/com/v1/domain/lostarksteam.com.

Who owns lostarksteam.com?

The registry did not return a person or a company for lostarksteam.com. RDAP often redacts the registrant. The registrar on file is Gname 363 Inc.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/lostarksteam.com at 2026-10-30T14:02:12Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:02:12Z
  • TLS source tls:443 at 2026-10-30T14:02:12Z
  • HTTP source https://lostarksteam.com/ at 2026-10-30T14:02:12Z
  • Tech source wappalyzergo at 2026-10-30T14:02:12Z
  • Geo source db-ip at 2026-10-30T14:02:12Z
  • Safety source family DNS and local lists at 2026-10-30T14:02:12Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com Gname 363 Inc

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.

Removal policy

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.