prem.de is registered with whois.denic.de and is hosted on AS6724 in Germany. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
0 of 4 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed prem.de. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
Is prem.de’s name taken on other extensions?
Every IP address prem.de resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| prem.de | 81.169.145.86 | 150 |
Other domains served from 81.169.145.86. Normal for shared hosting and CDNs.
No reviews yet. Used prem.de? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
prem.de has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
prem.de is registered through whois.denic.de. See WHOIS →
prem.de is served from 2 IP addresses, mainly on AS6724 in Germany. See Hosting →
Raw registry data for prem.de. May be redacted by privacy services.
Domain: prem.de Status: connect
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with prem.de. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 27 Oct 2026.