ytmp3.blue
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 88 days left5 years old
65
ytmp3.blue was registered on 20 Sep 2021 via Dynadot Inc and the registry expiry is 20 Sep 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/ytmp3.blue.
ytmp3.blue publishes 2 nameservers. DNSSEC is not signed.
ytmp3.blue has 1 IPv4 address (185.53.179.149). The geolocation database places 185.53.179.149 in Munich (Altstadt-Lehel), Germany.
The TLS certificate from YE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Caddy and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for ytmp3.blue in the checks that ran.
Domain · RDAP/WHOIS
ytmp3.blue was registered on 20 Sep 2021 via Dynadot Inc. The registry returned 2 status values and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/ytmp3.blue.
| Registered | since 20 Sep 2021 |
|---|---|
| Created | 20 September 2021 |
| Updated | 29 October 2026 |
| Expires | 20 September 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited, transfer period |
| Nameservers | ns1.dyna-ns.net, ns2.dyna-ns.net |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/ytmp3.blue |
ytmp3.blue 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 ytmp3.blue in the registration record from https://rdap.identitydigital.services/rdap/domain/ytmp3.blue.
Nameserver ns2.dyna-ns.net is published for ytmp3.blue in the registration record from https://rdap.identitydigital.services/rdap/domain/ytmp3.blue.
DNS
ytmp3.blue has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 185.53.179.149 |
|---|---|
| AAAA | — |
| NS | ns1.dyna-ns.net, ns2.dyna-ns.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 185.53.179.149 answers for ytmp3.blue at resolver 1.1.1.1:53.
A random label under ytmp3.blue also resolved, which means wildcard DNS is on.
Hosting and geo
ytmp3.blue is placed in Munich (Altstadt-Lehel), Germany by the local geolocation database (db-ip).
| Address | 185.53.179.149 |
|---|---|
| Country | Germany |
| City | Munich (Altstadt-Lehel) |
| Source | db-ip |
SSL/TLS
The certificate for ytmp3.blue is valid, with 88 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | ytmp3.blue |
| Valid from | 29 October 2026 |
| Valid until | 27 January 2027 |
| Days left | 88 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.ytmp3.blue, ytmp3.blue.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Caddy · Web servers
- HTTP/3 · Miscellaneous
Caddy is filed under Web servers.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 127 ms. The target title is 10 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 127 ms |
| Title length | 10 yes |
| Quoted title | "ytmp3.blue" |
| Meta description | "Die besten Informationen und wichtigsten Links zu allen Themen im Zusammenhang mit ytmp3.blue." yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | german |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 ytmp3.blue 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 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 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: geo city changed from empty to Munich (Altstadt-Lehel).
- October 2026: geo country changed from empty to Germany.
Questions
Is ytmp3.blue 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 ytmp3.blue?
ytmp3.blue is placed in Munich (Altstadt-Lehel), Germany.
When does ytmp3.blue expire?
ytmp3.blue expires on 20 September 2027 according to https://rdap.identitydigital.services/rdap/domain/ytmp3.blue.
Who owns ytmp3.blue?
The registry did not return a person or a company for ytmp3.blue. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/ytmp3.blue at 2026-10-30T13:33:00Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:33:00Z
- TLS source tls:443 at 2026-10-30T13:33:00Z
- HTTP source https://ytmp3.blue/ at 2026-10-30T13:33:00Z
- Tech source wappalyzergo at 2026-10-30T13:33:00Z
- Geo source db-ip at 2026-10-30T13:33:00Z
- Safety source family DNS and local lists at 2026-10-30T13:33:00Z
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.