gastromatic.space
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
90
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
90
gastromatic.space was registered on 23 May 2018 via InterNetX GmbH and the registry expiry is 23 May 2027. WHOIS data came from RDAP at https://rdap.radix.host/rdap/domain/gastromatic.space.
gastromatic.space publishes 3 nameservers. DNSSEC is not signed.
gastromatic.space has 1 IPv4 address (81.209.255.247) and 1 IPv6 address (2001:7f0:3000:512::512:247). The geolocation database places 81.209.255.247 in Hanover, Germany.
The TLS certificate from YR2 is valid and has 28 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Apache HTTP Server, HSTS, Nextcloud and PHP. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for gastromatic.space in the checks that ran.
gastromatic.space was registered on 23 May 2018 via InterNetX GmbH. The registry returned 1 status value and 3 nameservers from https://rdap.radix.host/rdap/domain/gastromatic.space.
| Registered | since 23 May 2018 |
|---|---|
| Created | 23 May 2018 |
| Updated | 8 July 2026 |
| Expires | 23 May 2027 |
| Registrar | InterNetX GmbH |
| Status | client transfer prohibited |
| Nameservers | ns6.pixelx.de, ns7.pixelx.de, ns8.pixelx.de |
| DNSSEC | no |
| Source | https://rdap.radix.host/rdap/domain/gastromatic.space |
gastromatic.space 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 ns6.pixelx.de is published for gastromatic.space in the registration record from https://rdap.radix.host/rdap/domain/gastromatic.space.
Nameserver ns7.pixelx.de is published for gastromatic.space in the registration record from https://rdap.radix.host/rdap/domain/gastromatic.space.
Nameserver ns8.pixelx.de is published for gastromatic.space in the registration record from https://rdap.radix.host/rdap/domain/gastromatic.space.
gastromatic.space has 2 address records, 1 mail exchanger and 3 nameservers, measured at 1.1.1.1:53.
| A | 81.209.255.247 |
|---|---|
| AAAA | 2001:7f0:3000:512::512:247 |
| NS | ns6.pixelx.de, ns7.pixelx.de, ns8.pixelx.de |
| MX | ncserver.gastromatic.space (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at gastromatic.space is "v=spf1 +a +mx +a:ncserver.gastromatic.space -all".
The DMARC text record at _dmarc.gastromatic.space is "v=DMARC1; p=quarantine; adkim=s; aspf=s".
IPv4 address 81.209.255.247 answers for gastromatic.space at resolver 1.1.1.1:53.
IPv6 address 2001:7f0:3000:512::512:247 answers for gastromatic.space at resolver 1.1.1.1:53.
Mail exchanger ncserver.gastromatic.space has preference 10.
gastromatic.space is placed in Hanover, Germany by the local geolocation database (db-ip).
| Address | 81.209.255.247 |
|---|---|
| Country | Germany |
| City | Hanover |
| Source | db-ip |
The certificate for gastromatic.space is valid, with 28 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | gastromatic.space |
| Valid from | 31 August 2026 |
| Valid until | 29 November 2026 |
| Days left | 28 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: gastromatic.space, www.gastromatic.space.
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
Apache HTTP Server is filed under Web servers.
HSTS is filed under Security.
Nextcloud is filed under Digital asset management, Miscellaneous.
PHP is filed under Programming languages.
The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for gastromatic.space 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 | yes |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
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 15 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
gastromatic.space is placed in Hanover, Germany.
gastromatic.space expires on 23 May 2027 according to https://rdap.radix.host/rdap/domain/gastromatic.space.
The registry did not return a person or a company for gastromatic.space. RDAP often redacts the registrant. The registrar on file is InterNetX GmbH.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.