bityli.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe7 years oldTranco #290785
40
bityli.com was registered on 23 Aug 2019 via Amazon Registrar, Inc. and the registry expiry is 23 Aug 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bityli.com.
bityli.com publishes 4 nameservers. DNSSEC is not signed.
No safety warning was recorded for bityli.com in the checks that ran.
Domain · RDAP/WHOIS
bityli.com was registered on 23 Aug 2019 via Amazon Registrar, Inc.. The registry returned 1 status value and 8 nameservers from https://rdap.verisign.com/com/v1/domain/bityli.com.
| Registered | since 23 Aug 2019 |
|---|---|
| Created | 23 August 2019 |
| Updated | 16 May 2026 |
| Expires | 23 August 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns-1405.awsdns-47.org, ns-1969.awsdns-54.co.uk, ns-308.awsdns-38.com, ns-809.awsdns-37.net, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/bityli.com |
bityli.com 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-1405.awsdns-47.org is published for bityli.com in the registration record from https://rdap.verisign.com/com/v1/domain/bityli.com.
Nameserver ns-1969.awsdns-54.co.uk is published for bityli.com in the registration record from https://rdap.verisign.com/com/v1/domain/bityli.com.
Nameserver ns-308.awsdns-38.com is published for bityli.com in the registration record from https://rdap.verisign.com/com/v1/domain/bityli.com.
Nameserver ns-809.awsdns-37.net is published for bityli.com in the registration record from https://rdap.verisign.com/com/v1/domain/bityli.com.
Nameserver ns-cloud-d1.googledomains.com is published for bityli.com in the registration record from https://rdap.verisign.com/com/v1/domain/bityli.com.
Nameserver ns-cloud-d2.googledomains.com is published for bityli.com in the registration record from https://rdap.verisign.com/com/v1/domain/bityli.com.
Nameserver ns-cloud-d3.googledomains.com is published for bityli.com in the registration record from https://rdap.verisign.com/com/v1/domain/bityli.com.
Nameserver ns-cloud-d4.googledomains.com is published for bityli.com in the registration record from https://rdap.verisign.com/com/v1/domain/bityli.com.
DNS
bityli.com has 0 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com |
| MX | — |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at bityli.com is "v=spf1 -all".
The DMARC text record at _dmarc.bityli.com is "v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1;".
Hosting and geo
Geolocation for bityli.com is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
SSL/TLS
No TLS certificate was read for bityli.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup bityli.com on 46.38.252.230:53: no such host
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://bityli.com/": dial tcp: lookup bityli.com on 46.38.252.230:53: no such host
Security
Family DNS for bityli.com 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 10 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
First checked on 30 October 2026; changes will appear here.
Questions
Is bityli.com 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 bityli.com?
The host network is not available without a local geolocation database.
When does bityli.com expire?
bityli.com expires on 23 August 2027 according to https://rdap.verisign.com/com/v1/domain/bityli.com.
Who owns bityli.com?
The registry did not return a person or a company for bityli.com. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/bityli.com at 2026-10-30T13:47:14Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:47:14Z
- TLS source tls:443 at 2026-10-30T13:47:14Z
- HTTP source https://bityli.com/ at 2026-10-30T13:47:14Z
- Tech source not available at 2026-10-30T13:47:14Z
- Geo source db-ip at 2026-10-30T13:47:14Z
- Safety source family DNS and local lists at 2026-10-30T13:47:14Z
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.