4max.de
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of 4max.de
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
DNS Records
WHOIS / Registration
Registration data planned
Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.
Subdomains
Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.
| Subdomain | Resolves to | Last seen |
|---|---|---|
| 4max.de | 2026-08-25 23:18:50.791 | |
| www.4max.de | 2026-08-21 05:43:03.927 | |
| mail.4max.de | DNS pending | — |
| mail.comune.4max.de | DNS pending | — |
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
Certificate observations pending
TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.
IPs Citing This Domain
No citing IPs found yet
As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.
Origin / IP-Leak
When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.
No origin-IP leaks detected (yet)
Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.
CT-Log Evidence
Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.
Threat Intelligence
Domain threat-intel pending
Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.
History
Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.
| Type | Value | First seen | Last seen |
|---|---|---|---|
| CAA | 0 issuewild ";" | 2026-06-22 07:48:15.601 | 2026-08-25 23:18:50.791 |
| TXT | v=spf1 -all | 2026-06-22 07:48:15.601 | 2026-08-25 23:18:50.791 |
| CAA | 0 issue "letsencrypt.org;validationmethods=http-01" | 2026-06-22 07:48:15.601 | 2026-07-17 10:24:28.026 |
| A | 209.38.54.191 | 2026-06-22 07:48:15.601 | 2026-07-17 10:24:28.026 |
| CAA | 0 issuevmc ";" | 2026-06-22 07:48:15.601 | 2026-08-25 23:18:50.791 |
| NS | ns5.nameshift.com | 2026-06-22 07:48:15.601 | 2026-08-25 23:18:50.791 |
| AAAA | 2a03:b0c0:2:f0::fc3a:e001 | 2026-06-22 07:48:15.601 | 2026-07-17 10:24:28.026 |
| NS | ns4.nameshift.com | 2026-06-22 07:48:15.601 | 2026-08-25 23:18:50.791 |
| CAA | 0 issuemail ";" | 2026-06-22 07:48:15.601 | 2026-08-25 23:18:50.791 |
| CAA | 0 issue "pki.goog;validationmethods=http-01" | 2026-06-22 07:48:15.601 | 2026-07-17 10:24:28.026 |
| A | 5.83.210.1 | 2026-08-21 05:43:03.927 | 2026-08-25 23:18:50.791 |
| AAAA | 2a0e:4001:11::1 | 2026-08-21 05:43:03.927 | 2026-08-25 23:18:50.791 |
| CAA | 0 issue "letsencrypt.org;validationmethods=http-01,dns-01" | 2026-08-21 05:43:03.927 | 2026-08-25 23:18:50.791 |
| CAA | 0 issue "pki.goog;validationmethods=http-01,dns-01" | 2026-08-21 05:43:03.927 | 2026-08-25 23:18:50.791 |