foodify.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 82 days left20 years old
80
foodify.com was registered on 19 Jun 2006 via Key-Systems GmbH and the registry expiry is 19 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/foodify.com.
foodify.com publishes 2 nameservers. DNSSEC is not signed.
foodify.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 82 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS, HTTP/3, Node.js, Nuxt.js, Vercel and Vue.js. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for foodify.com in the checks that ran.
Domain · RDAP/WHOIS
foodify.com was registered on 19 Jun 2006 via Key-Systems GmbH. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/foodify.com.
| Registered | since 19 Jun 2006 |
|---|---|
| Created | 19 June 2006 |
| Updated | 21 June 2026 |
| Expires | 19 June 2027 |
| Registrar | Key-Systems GmbH |
| Status | client transfer prohibited |
| Nameservers | alexa.ns.cloudflare.com, dion.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/foodify.com |
foodify.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 alexa.ns.cloudflare.com is published for foodify.com in the registration record from https://rdap.verisign.com/com/v1/domain/foodify.com.
Nameserver dion.ns.cloudflare.com is published for foodify.com in the registration record from https://rdap.verisign.com/com/v1/domain/foodify.com.
DNS
foodify.com has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | alexa.ns.cloudflare.com, dion.ns.cloudflare.com |
| MX | rekeep.esvacloud.com (5), rekeep02.esvacloud.com (5) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at foodify.com is "v=spf1 include:rekeep.esvacloud.com include:rekeep02.esvacloud.com include:spf.protection.outlook.com include:sendgrid.net -all".
The DMARC text record at _dmarc.foodify.com is "v=DMARC1; p=quarantine; sp=quarantine; pct=100; rua=mailto:[email protected]".
IPv4 address 188.114.96.4 answers for foodify.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for foodify.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for foodify.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for foodify.com at resolver 1.1.1.1:53.
Mail exchanger rekeep.esvacloud.com has preference 5.
Mail exchanger rekeep02.esvacloud.com has preference 5.
A random label under foodify.com also resolved, which means wildcard DNS is on.
Hosting and geo
foodify.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for foodify.com is valid, with 82 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | foodify.com |
| Valid from | 23 October 2026 |
| Valid until | 22 January 2027 |
| Days left | 82 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.foodify.com, foodify.com.
Tech stack
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
- Cloudflare · CDN
- HSTS · Security
- HTTP/3 · Miscellaneous
- Node.js · Programming languages
- Nuxt.js · JavaScript frameworks, Web frameworks, Web servers, Static site generator
- Vercel · PaaS
- Vue.js · JavaScript frameworks
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Node.js is filed under Programming languages.
Nuxt.js is filed under JavaScript frameworks, Web frameworks, Web servers, Static site generator.
Vercel is filed under PaaS.
Vue.js is filed under JavaScript frameworks.
On-page checks
The homepage returned HTTP 200 in 133 ms. The target title is 31 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 133 ms |
| Title length | 31 yes |
| Quoted title | "Foodify ｜ Mądry catering domowy" |
| Meta description | "Foodify to mądry catering domowy dopasowujący się do Ciebie i Twojej rodziny. Wybieraj posiłki, korzystaj z e-Asystenta AI i ciesz się smakiem!" yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | https://foodify.com/pl |
| Language | pl-PL |
| Links | 60 |
| Images | 53 |
| 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 foodify.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
- October 2026: dns a changed from 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
Questions
Is foodify.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 foodify.com?
foodify.com is placed in Toronto, Canada.
When does foodify.com expire?
foodify.com expires on 19 June 2027 according to https://rdap.verisign.com/com/v1/domain/foodify.com.
Who owns foodify.com?
The registry did not return a person or a company for foodify.com. RDAP often redacts the registrant. The registrar on file is Key-Systems GmbH.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/foodify.com at 2026-10-30T13:54:51Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:54:51Z
- TLS source tls:443 at 2026-10-30T13:54:51Z
- HTTP source https://foodify.com/ at 2026-10-30T13:54:51Z
- Tech source wappalyzergo at 2026-10-30T13:54:51Z
- Geo source db-ip at 2026-10-30T13:54:51Z
- Safety source family DNS and local lists at 2026-10-30T13:54:51Z
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.