tenniskafe.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 61 days left17 years oldTranco #313286
80
tenniskafe.com was registered on 13 Apr 2009 via PDR Ltd. d/b/a PublicDomainRegistry.com and the registry expiry is 13 Apr 2029. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/tenniskafe.com.
tenniskafe.com publishes 2 nameservers. DNSSEC is not signed.
tenniskafe.com has 2 IPv4 addresses (104.21.76.62, 172.67.190.86) and 2 IPv6 addresses (2606:4700:3032::ac43:be56, 2606:4700:3034::6815:4c3e). The geolocation database places 104.21.76.62 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 61 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Cloudflare Browser Insights, Google Publisher Tag, Google Tag Manager, HSTS, HTTP/3, MySQL, PHP, W3 Total Cache, WordPress and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for tenniskafe.com in the checks that ran.
Domain · RDAP/WHOIS
tenniskafe.com was registered on 13 Apr 2009 via PDR Ltd. d/b/a PublicDomainRegistry.com. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/tenniskafe.com.
| Registered | since 13 Apr 2009 |
|---|---|
| Created | 13 April 2009 |
| Updated | 13 April 2024 |
| Expires | 13 April 2029 |
| Registrar | PDR Ltd. d/b/a PublicDomainRegistry.com |
| Status | client transfer prohibited |
| Nameservers | max.ns.cloudflare.com, vera.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/tenniskafe.com |
tenniskafe.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 max.ns.cloudflare.com is published for tenniskafe.com in the registration record from https://rdap.verisign.com/com/v1/domain/tenniskafe.com.
Nameserver vera.ns.cloudflare.com is published for tenniskafe.com in the registration record from https://rdap.verisign.com/com/v1/domain/tenniskafe.com.
DNS
tenniskafe.com has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.76.62, 172.67.190.86 |
|---|---|
| AAAA | 2606:4700:3032::ac43:be56, 2606:4700:3034::6815:4c3e |
| NS | max.ns.cloudflare.com, vera.ns.cloudflare.com |
| MX | mail.tenniskafe.com (0) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at tenniskafe.com is "v=spf1 +a +mx +ip4:79.124.76.130 -all".
The DMARC text record at _dmarc.tenniskafe.com is "v=DMARC1; p=reject; sp=none; rf=afrf; pct=100; ri=86400".
IPv4 address 104.21.76.62 answers for tenniskafe.com at resolver 1.1.1.1:53.
IPv4 address 172.67.190.86 answers for tenniskafe.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::ac43:be56 answers for tenniskafe.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::6815:4c3e answers for tenniskafe.com at resolver 1.1.1.1:53.
Mail exchanger mail.tenniskafe.com has preference 0.
A random label under tenniskafe.com also resolved, which means wildcard DNS is on.
Hosting and geo
tenniskafe.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.76.62 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for tenniskafe.com is valid, with 61 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | tenniskafe.com |
| Valid from | 2 October 2026 |
| Valid until | 31 December 2026 |
| Days left | 61 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.tenniskafe.com, tenniskafe.com.
Tech stack
Tech detection checked the fetched homepage and named 12 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- Google Publisher Tag · Advertising
- Google Tag Manager · Tag managers
- HSTS · Security
- HTTP/3 · Miscellaneous
- MySQL · Databases
- PHP · Programming languages
- W3 Total Cache · Caching, WordPress plugins
- WordPress · CMS, Blogs
- jQuery · JavaScript libraries
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Publisher Tag is filed under Advertising.
Google Tag Manager is filed under Tag managers.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
W3 Total Cache is filed under Caching, WordPress plugins.
WordPress is filed under CMS, Blogs.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 267 ms. The target title is 134 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 267 ms |
| Title length | 134 no |
| Quoted title | "TennisKafe – Тенис Кафе – най-големият тенис портал в България. Тенис новини, резултати, турнири, гледайте мачове на живо по интернет." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | max-image-preview:large |
| Canonical | https://www.tenniskafe.com/ |
| Language | bg-BG |
| Links | 148 |
| Images | 35 |
| 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 tenniskafe.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 | yes |
| 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 10 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 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 tenniskafe.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 tenniskafe.com?
tenniskafe.com is placed in Toronto, Canada.
When does tenniskafe.com expire?
tenniskafe.com expires on 13 April 2029 according to https://rdap.verisign.com/com/v1/domain/tenniskafe.com.
Who owns tenniskafe.com?
The registry did not return a person or a company for tenniskafe.com. RDAP often redacts the registrant. The registrar on file is PDR Ltd. d/b/a PublicDomainRegistry.com.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/tenniskafe.com at 2026-10-30T14:16:15Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:16:15Z
- TLS source tls:443 at 2026-10-30T14:16:15Z
- HTTP source https://tenniskafe.com/ at 2026-10-30T14:16:15Z
- Tech source wappalyzergo at 2026-10-30T14:16:15Z
- Geo source db-ip at 2026-10-30T14:16:15Z
- Safety source family DNS and local lists at 2026-10-30T14:16:15Z
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.