mydesi.live

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

HTTP 429Family DNS blockedSSL: 30 days left4 years old

One re-check per domain each UTC day.

35

mydesi.live was registered on 7 Aug 2022 via NameSilo, LLC and the registry expiry is 7 Aug 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/mydesi.live.

mydesi.live publishes 2 nameservers. DNSSEC is not signed.

mydesi.live has 1 IPv4 address (37.48.77.83). The geolocation database places 37.48.77.83 in Amsterdam, The Netherlands.

The TLS certificate from YR2 is valid and has 30 days left (TLS 1.3).

Tech detection named Cowboy and Erlang. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

mydesi.live was registered on 7 Aug 2022 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/mydesi.live.

Registeredsince 7 Aug 2022
Created7 August 2022
Updated21 September 2026
Expires7 August 2027
RegistrarNameSilo, LLC
Statusclient transfer prohibited
Nameserversns1.brainydns.com, ns2.brainydns.com
DNSSECno
Sourcehttps://rdap.identitydigital.services/rdap/domain/mydesi.live

mydesi.live 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 ns1.brainydns.com is published for mydesi.live in the registration record from https://rdap.identitydigital.services/rdap/domain/mydesi.live.

Nameserver ns2.brainydns.com is published for mydesi.live in the registration record from https://rdap.identitydigital.services/rdap/domain/mydesi.live.

DNS

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

A37.48.77.83
AAAA—
NSns1.koaladns.com, ns2.koaladns.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 37.48.77.83 answers for mydesi.live at resolver 1.1.1.1:53.

A random label under mydesi.live also resolved, which means wildcard DNS is on.

Hosting and geo

mydesi.live is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).

Address37.48.77.83
CountryThe Netherlands
CityAmsterdam
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for mydesi.live is valid, with 30 days left and 2 subject alternative names. Source: tls:443.

IssuerYR2
Subjectmydesi.live
Valid from2 September 2026
Valid until1 December 2026
Days left30
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.mydesi.live, mydesi.live.

Tech stack

Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.

  • Cowboy · Web servers
  • Erlang · Programming languages

Cowboy is filed under Web servers.

Erlang is filed under Programming languages.

On-page checks

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

Status429
TTFB18 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links0
Images0
Faviconno

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

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

Cloudflare family DNS returned a block for mydesi.live. 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 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 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

  • October 2026: dns a changed from 212.92.104.10 to 37.48.77.83.
  • October 2026: dns ns changed from ns1.kirklanddc.com,ns2.kirklanddc.com to ns1.koaladns.com,ns2.koaladns.com.
  • October 2026: geo city changed from empty to Amsterdam.
  • October 2026: geo country changed from empty to The Netherlands.

Questions

Is mydesi.live safe?

Cloudflare family DNS returned a block for mydesi.live. That resolver covers adult and malware names.

Who hosts mydesi.live?

mydesi.live is placed in Amsterdam, The Netherlands.

When does mydesi.live expire?

mydesi.live expires on 7 August 2027 according to https://rdap.identitydigital.services/rdap/domain/mydesi.live.

Who owns mydesi.live?

The registry did not return a person or a company for mydesi.live. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.

Sources

  • RDAP source https://rdap.identitydigital.services/rdap/domain/mydesi.live at 2026-10-30T14:42:29Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:42:29Z
  • TLS source tls:443 at 2026-10-30T14:42:29Z
  • HTTP source https://mydesi.live/ at 2026-10-30T14:42:29Z
  • Tech source wappalyzergo at 2026-10-30T14:42:29Z
  • Geo source db-ip at 2026-10-30T14:42:29Z
  • Safety source family DNS and local lists at 2026-10-30T14:42:29Z

Methodology

Related reports

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

.live NameSilo, LLC

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.