didisiiwa.life

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

Online · 200SafeSSL: 58 days leftUnder 1 year old

One re-check per domain each UTC day.

67

didisiiwa.life was registered on 3 Dec 2025 via Dynadot Inc and the registry expiry is 3 Dec 2026. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/didisiiwa.life.

didisiiwa.life publishes 2 nameservers. DNSSEC is not signed.

didisiiwa.life has 1 IPv4 address (54.215.31.113). The geolocation database places 54.215.31.113 in San Jose, United States.

The TLS certificate from YR1 is valid and has 58 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for didisiiwa.life in the checks that ran.

Domain · RDAP/WHOIS

didisiiwa.life was registered on 3 Dec 2025 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/didisiiwa.life.

Registeredsince 3 Dec 2025
Created3 December 2025
Updated12 August 2026
Expires3 December 2026
RegistrarDynadot Inc
Statusclient transfer prohibited
Nameserversns1.dyna-ns.net, ns2.dyna-ns.net
DNSSECno
Sourcehttps://rdap.identitydigital.services/rdap/domain/didisiiwa.life

didisiiwa.life 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.dyna-ns.net is published for didisiiwa.life in the registration record from https://rdap.identitydigital.services/rdap/domain/didisiiwa.life.

Nameserver ns2.dyna-ns.net is published for didisiiwa.life in the registration record from https://rdap.identitydigital.services/rdap/domain/didisiiwa.life.

DNS

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

A54.215.31.113
AAAA—
NSns1.dyna-ns.net, ns2.dyna-ns.net
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 54.215.31.113 answers for didisiiwa.life at resolver 1.1.1.1:53.

Hosting and geo

didisiiwa.life is placed in San Jose, United States by the local geolocation database (db-ip).

Address54.215.31.113
CountryUnited States
CitySan Jose
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for didisiiwa.life is valid, with 58 days left and 2 subject alternative names. Source: tls:443.

IssuerYR1
Subjectdidisiiwa.life
Valid from29 September 2026
Valid until28 December 2026
Days left58
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.didisiiwa.life, didisiiwa.life.

Tech stack

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

  • Cloudflare · CDN
  • HSTS · Security
  • HTTP/3 · Miscellaneous

Cloudflare is filed under CDN.

HSTS is filed under Security.

HTTP/3 is filed under Miscellaneous.

On-page checks

The homepage returned HTTP 200 in 169 ms. The target title is 4 characters and the page has 0 H1 headings.

Status200
TTFB169 ms
Title length4 yes
Quoted title"最新视频"
Meta descriptionnone no
H1 count0
HSTSyes yes
CSPno
X-Frame-Options—
Robots metanoarchive
Canonical—
Language—
Links1
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 didisiiwa.life is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
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 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 5 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: http hsts changed from false to true.
  • October 2026: tech added HSTS.
  • October 2026: geo city changed from empty to San Jose.
  • October 2026: geo country changed from empty to United States.

Questions

Is didisiiwa.life 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 didisiiwa.life?

didisiiwa.life is placed in San Jose, United States.

When does didisiiwa.life expire?

didisiiwa.life expires on 3 December 2026 according to https://rdap.identitydigital.services/rdap/domain/didisiiwa.life.

Who owns didisiiwa.life?

The registry did not return a person or a company for didisiiwa.life. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.

Sources

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

Methodology

Related reports

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

.life Dynadot 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.