Check-Host.cc

Try 1.1.1.1 AS13335 check-host.cc /country/de /tld/cc
Domain

evilbit.de

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

DNS Check HTTP Check Run Full Scan .de TLD

Run a live full scan of evilbit.de

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
5
A/AAAA targets
Subdomains
3
CT + scan + body
Record Types
5
seen in DNS
Observed Certs
4
in our scans

DNS Records

A
91.223.231.146
AAAA
2001:67c:8a4:5000::80
MX
10 mail.evilbit.de
NS
boa.amplitut.de, mask.amplitut.de, ns.evilbit.de
TXT
google-site-verification=sgdSvUaL9gpXyy9yFKE_A0W2EKVWfMJ3S-hC1hTXysc, v=spf1 ip4:91.223.231.146 ip6:2001:67c:8a4:5000::0/64 ip4:5.75.244.113 ip6:2a01:4f8:c012:1000::1/128 ~all, yahoo-verification-key=5yaW0n/EQO/2Zxd4s9ZaLUSxiczXAig5yF1WCgoVOnc=
CNAME
—
CAA
—

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
evilbit.de
91.223.231.146 2001:67c:8a4:5000::80
2026-07-18 02:05:53.025
mail.evilbit.de
91.223.231.146 2001:67c:8a4:5000::25
2026-07-28 02:58:03.815
misp.evilbit.de
77.90.2.141 2a0a:51c1:9:e2::a
2026-06-17 17:08:49.411

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

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

104.225.216.71:8000 href · ×2

Origin / IP-Leak

USP

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.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.