byrdle.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 67 days left4 years old
65
byrdle.net was registered on 31 Jan 2022 via Tucows Domains Inc. and the registry expiry is 31 Jan 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/byrdle.net.
byrdle.net publishes 4 nameservers. DNSSEC is not signed.
byrdle.net has 4 IPv4 addresses (18.65.39.101, 18.65.39.117, 18.65.39.35, 18.65.39.54). The geolocation database places 18.65.39.101 in Dublin, Ireland.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 67 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon S3, Amazon Web Services, Google Analytics and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for byrdle.net in the checks that ran.
Domain · RDAP/WHOIS
byrdle.net was registered on 31 Jan 2022 via Tucows Domains Inc.. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/net/v1/domain/byrdle.net.
| Registered | since 31 Jan 2022 |
|---|---|
| Created | 31 January 2022 |
| Updated | 31 January 2026 |
| Expires | 31 January 2027 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | ns-133.awsdns-16.com, ns-1403.awsdns-47.org, ns-1797.awsdns-32.co.uk, ns-814.awsdns-37.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/byrdle.net |
byrdle.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.
byrdle.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns-133.awsdns-16.com is published for byrdle.net in the registration record from https://rdap.verisign.com/net/v1/domain/byrdle.net.
Nameserver ns-1403.awsdns-47.org is published for byrdle.net in the registration record from https://rdap.verisign.com/net/v1/domain/byrdle.net.
Nameserver ns-1797.awsdns-32.co.uk is published for byrdle.net in the registration record from https://rdap.verisign.com/net/v1/domain/byrdle.net.
Nameserver ns-814.awsdns-37.net is published for byrdle.net in the registration record from https://rdap.verisign.com/net/v1/domain/byrdle.net.
DNS
byrdle.net has 4 address records, 2 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 18.65.39.101, 18.65.39.117, 18.65.39.35, 18.65.39.54 |
|---|---|
| AAAA | — |
| NS | ns-133.awsdns-16.com, ns-1403.awsdns-47.org, ns-1797.awsdns-32.co.uk, ns-814.awsdns-37.net |
| MX | mx0.123-reg.co.uk (10), mx1.123-reg.co.uk (20) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 18.65.39.101 answers for byrdle.net at resolver 1.1.1.1:53.
IPv4 address 18.65.39.117 answers for byrdle.net at resolver 1.1.1.1:53.
IPv4 address 18.65.39.35 answers for byrdle.net at resolver 1.1.1.1:53.
IPv4 address 18.65.39.54 answers for byrdle.net at resolver 1.1.1.1:53.
Mail exchanger mx0.123-reg.co.uk has preference 10.
Mail exchanger mx1.123-reg.co.uk has preference 20.
Hosting and geo
byrdle.net is placed in Dublin, Ireland by the local geolocation database (db-ip).
| Address | 18.65.39.101 |
|---|---|
| Country | Ireland |
| City | Dublin |
| Source | db-ip |
SSL/TLS
The certificate for byrdle.net is valid, with 67 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | *.byrdle.net |
| Valid from | 8 December 2025 |
| Valid until | 6 January 2027 |
| Days left | 67 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.byrdle.net, byrdle.net.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Amazon CloudFront · CDN
- Amazon S3 · CDN
- Amazon Web Services · PaaS
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
Amazon CloudFront is filed under CDN.
Amazon S3 is filed under CDN.
Amazon Web Services is filed under PaaS.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 118 ms. The target title is 38 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 118 ms |
| Title length | 38 yes |
| Quoted title | "Byrdle - the choral word guessing game" |
| Meta description | "Guess the hidden choral-themed word in 6 tries. A new puzzle is available each day." yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 0 |
| 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 byrdle.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 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: dns a changed from 18.172.112.103,18.172.112.13,18.172.112.81,18.172.112.89 to 18.65.39.101,18.65.39.117,18.65.39.35,18.65.39.54.
Questions
Is byrdle.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 byrdle.net?
byrdle.net is placed in Dublin, Ireland.
When does byrdle.net expire?
byrdle.net expires on 31 January 2027 according to https://rdap.verisign.com/net/v1/domain/byrdle.net.
Who owns byrdle.net?
The registry did not return a person or a company for byrdle.net. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/byrdle.net at 2026-10-30T14:50:57Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:50:57Z
- TLS source tls:443 at 2026-10-30T14:50:57Z
- HTTP source https://byrdle.net/ at 2026-10-30T14:50:57Z
- Tech source wappalyzergo at 2026-10-30T14:50:57Z
- Geo source db-ip at 2026-10-30T14:50:57Z
- Safety source family DNS and local lists at 2026-10-30T14:50:57Z
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.