limeshark.dev
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 67 days left2 years old
35
limeshark.dev was registered on 13 Mar 2024 via Spaceship, Inc. and the registry expiry is 13 Mar 2027. WHOIS data came from RDAP at https://pubapi.registry.google/rdap/domain/limeshark.dev.
limeshark.dev publishes 2 nameservers. DNSSEC is not signed.
limeshark.dev has 1 IPv4 address (162.4.84.215). The geolocation database places 162.4.84.215 in Los Angeles, United States.
The TLS certificate from YE2 is not valid (TLS 1.3).
No safety warning was recorded for limeshark.dev in the checks that ran.
Domain · RDAP/WHOIS
limeshark.dev was registered on 13 Mar 2024 via Spaceship, Inc.. The registry returned 1 status value and 2 nameservers from https://pubapi.registry.google/rdap/domain/limeshark.dev.
| Registered | since 13 Mar 2024 |
|---|---|
| Created | 13 March 2024 |
| Updated | 26 March 2026 |
| Expires | 13 March 2027 |
| Registrar | Spaceship, Inc. |
| Status | client transfer prohibited |
| Nameservers | a.2ns.net, b.2ns.net |
| DNSSEC | no |
| Source | https://pubapi.registry.google/rdap/domain/limeshark.dev |
limeshark.dev 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 limeshark.dev in the registration record from https://pubapi.registry.google/rdap/domain/limeshark.dev.
Nameserver b.2ns.net is published for limeshark.dev in the registration record from https://pubapi.registry.google/rdap/domain/limeshark.dev.
DNS
limeshark.dev 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 limeshark.dev is "v=spf1 ip6:fd18:d113:9bed::/48 -all".
IPv4 address 162.4.84.215 answers for limeshark.dev at resolver 1.1.1.1:53.
Mail exchanger mail.hope-mail.com has preference 1.
A random label under limeshark.dev also resolved, which means wildcard DNS is on.
Hosting and geo
limeshark.dev 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
The certificate for limeshark.dev is not valid, with 67 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | limeshark.dev |
| Valid from | 9 October 2026 |
| Valid until | 7 January 2027 |
| Days left | 67 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: limeshark.dev.
Validation result: certificate did not validate
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://limeshark.dev/": tls: failed to verify certificate: x509: certificate signed by unknown authority
Security
Family DNS for limeshark.dev 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: tls issuer changed from empty to YE2.
- October 2026: tls not_after changed from empty to 2027-01-07T05:04:31Z.
- October 2026: tls protocol changed from empty to TLS 1.3.
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is limeshark.dev 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 limeshark.dev?
limeshark.dev is placed in Los Angeles, United States.
When does limeshark.dev expire?
limeshark.dev expires on 13 March 2027 according to https://pubapi.registry.google/rdap/domain/limeshark.dev.
Who owns limeshark.dev?
The registry did not return a person or a company for limeshark.dev. RDAP often redacts the registrant. The registrar on file is Spaceship, Inc..
Sources
- RDAP source https://pubapi.registry.google/rdap/domain/limeshark.dev at 2026-10-30T14:26:46Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:26:46Z
- TLS source tls:443 at 2026-10-30T14:26:46Z
- HTTP source https://limeshark.dev/ at 2026-10-30T14:26:46Z
- Tech source not available at 2026-10-30T14:26:46Z
- Geo source db-ip at 2026-10-30T14:26:46Z
- Safety source family DNS and local lists at 2026-10-30T14:26:46Z
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.