mylush.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 55 days left17 years old
70
mylush.net was registered on 5 Mar 2009 via Amazon Registrar, Inc. and the registry expiry is 5 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/mylush.net.
mylush.net publishes 4 nameservers. DNSSEC is not signed.
mylush.net has 4 IPv4 addresses (18.244.18.20, 18.244.18.26, 18.244.18.58, 18.244.18.82) and 8 IPv6 addresses (2600:9000:275d:1000:19:e925:9180:93a1, 2600:9000:275d:3a00:19:e925:9180:93a1, 2600:9000:275d:5a00:19:e925:9180:93a1, 2600:9000:275d:600:19:e925:9180:93a1, 2600:9000:275d:7c00:19:e925:9180:93a1, 2600:9000:275d:8c00:19:e925:9180:93a1, 2600:9000:275d:e800:19:e925:9180:93a1, 2600:9000:275d:f400:19:e925:9180:93a1). The geolocation database places 18.244.18.20 in Frankfurt am Main, Germany.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 55 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon S3, Amazon Web Services and Google AdSense. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for mylush.net in the checks that ran.
Domain · RDAP/WHOIS
mylush.net was registered on 5 Mar 2009 via Amazon Registrar, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/net/v1/domain/mylush.net.
| Registered | since 5 Mar 2009 |
|---|---|
| Created | 5 March 2009 |
| Updated | 11 June 2026 |
| Expires | 5 March 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns-1243.awsdns-27.org, ns-1826.awsdns-36.co.uk, ns-6.awsdns-00.com, ns-622.awsdns-13.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/mylush.net |
mylush.net 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 ns-1243.awsdns-27.org is published for mylush.net in the registration record from https://rdap.verisign.com/net/v1/domain/mylush.net.
Nameserver ns-1826.awsdns-36.co.uk is published for mylush.net in the registration record from https://rdap.verisign.com/net/v1/domain/mylush.net.
Nameserver ns-6.awsdns-00.com is published for mylush.net in the registration record from https://rdap.verisign.com/net/v1/domain/mylush.net.
Nameserver ns-622.awsdns-13.net is published for mylush.net in the registration record from https://rdap.verisign.com/net/v1/domain/mylush.net.
DNS
mylush.net has 12 address records, 2 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 18.244.18.20, 18.244.18.26, 18.244.18.58, 18.244.18.82 |
|---|---|
| AAAA | 2600:9000:275d:1000:19:e925:9180:93a1, 2600:9000:275d:3a00:19:e925:9180:93a1, 2600:9000:275d:5a00:19:e925:9180:93a1, 2600:9000:275d:600:19:e925:9180:93a1, 2600:9000:275d:7c00:19:e925:9180:93a1, 2600:9000:275d:8c00:19:e925:9180:93a1, 2600:9000:275d:e800:19:e925:9180:93a1, 2600:9000:275d:f400:19:e925:9180:93a1 |
| NS | ns-1243.awsdns-27.org, ns-1826.awsdns-36.co.uk, ns-6.awsdns-00.com, ns-622.awsdns-13.net |
| MX | mx1.forwardemail.net (0), mx2.forwardemail.net (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at mylush.net is "v=spf1 include:mailgun.org ~all".
IPv4 address 18.244.18.20 answers for mylush.net at resolver 1.1.1.1:53.
IPv4 address 18.244.18.26 answers for mylush.net at resolver 1.1.1.1:53.
IPv4 address 18.244.18.58 answers for mylush.net at resolver 1.1.1.1:53.
IPv4 address 18.244.18.82 answers for mylush.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:275d:1000:19:e925:9180:93a1 answers for mylush.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:275d:3a00:19:e925:9180:93a1 answers for mylush.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:275d:5a00:19:e925:9180:93a1 answers for mylush.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:275d:600:19:e925:9180:93a1 answers for mylush.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:275d:7c00:19:e925:9180:93a1 answers for mylush.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:275d:8c00:19:e925:9180:93a1 answers for mylush.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:275d:e800:19:e925:9180:93a1 answers for mylush.net at resolver 1.1.1.1:53.
IPv6 address 2600:9000:275d:f400:19:e925:9180:93a1 answers for mylush.net at resolver 1.1.1.1:53.
Mail exchanger mx1.forwardemail.net has preference 0.
Mail exchanger mx2.forwardemail.net has preference 0.
A random label under mylush.net also resolved, which means wildcard DNS is on.
Hosting and geo
mylush.net is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 18.244.18.20 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
The certificate for mylush.net is valid, with 55 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | mylush.net |
| Valid from | 11 June 2026 |
| Valid until | 25 December 2026 |
| Days left | 55 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: mylush.net, www.mylush.net.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Amazon CloudFront · CDN
- Amazon S3 · CDN
- Amazon Web Services · PaaS
- Google AdSense · Advertising
Amazon CloudFront is filed under CDN.
Amazon S3 is filed under CDN.
Amazon Web Services is filed under PaaS.
Google AdSense is filed under Advertising.
On-page checks
The homepage returned HTTP 200 in 6 ms. The target title is 74 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 6 ms |
| Title length | 74 no |
| Quoted title | "לוּחַ שָׁנָה עברי לועזי | דפדוף מהיר בלוח | תצוגת שלושה חודשים | דו כיווני" |
| Meta description | "הכי מהיר ברשת בין חודשי השנה | לוח שנה לועזי עברי בתצוגה תלת-חודשית, מימין לשמאל ולהיפך, תצוגה שנתית והדפסה, בלוח השנה תאריך עברי, פרשיות השבוע, חגים, והערות אישיות" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | /index.html |
| Language | he-IL |
| Links | 42 |
| Images | 0 |
| Favicon | yes |
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 mylush.net 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 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: dns aaaa changed from 2600:9000:275d:1600:19:e925:9180:93a1,2600:9000:275d:3000:19:e925:9180:93a1,2600:9000:275d:5800:19:e925:9180:93a1,2600:9000:275d:6400:19:e925:9180:93a1,2600:9000:275d:6c00:19:e925:9180:93a1,2600:9000:275d:6e00:19:e925:9180:93a1,2600:9000:275d:9400:19:e925:9180:93a1,2600:9000:275d:d400:19:e925:9180:93a1 to 2600:9000:275d:1000:19:e925:9180:93a1,2600:9000:275d:3a00:19:e925:9180:93a1,2600:9000:275d:5a00:19:e925:9180:93a1,2600:9000:275d:600:19:e925:9180:93a1,2600:9000:275d:7c00:19:e925:9180:93a1,2600:9000:275d:8c00:19:e925:9180:93a1,2600:9000:275d:e800:19:e925:9180:93a1,2600:9000:275d:f400:19:e925:9180:93a1.
Questions
Is mylush.net 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 mylush.net?
mylush.net is placed in Frankfurt am Main, Germany.
When does mylush.net expire?
mylush.net expires on 5 March 2027 according to https://rdap.verisign.com/net/v1/domain/mylush.net.
Who owns mylush.net?
The registry did not return a person or a company for mylush.net. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, Inc..
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/mylush.net at 2026-10-30T14:54:20Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:54:20Z
- TLS source tls:443 at 2026-10-30T14:54:20Z
- HTTP source https://mylush.net/ at 2026-10-30T14:54:20Z
- Tech source wappalyzergo at 2026-10-30T14:54:20Z
- Geo source db-ip at 2026-10-30T14:54:20Z
- Safety source family DNS and local lists at 2026-10-30T14:54:20Z
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.