manuel-herrmann.de

Observed Aug 11, 2026, 06:28 UTC (4d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of manuel-herrmann.de was taken 4d ago

manuel-herrmann.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting manuel-herrmann.de under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch manuel-herrmann.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
Also usesGoogle Search ConsoleKeybase
IPv6 · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 03:04 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat manuel-herrmann.de actually stands on - every host below is a signed observation
manuel-herrmann.de
A / AAAA
144.76.237.30162.55.3.185176.9.219.86213.239.204.83+4 more
2a01serves the site
NS
ns1.0x17.dens2.0x17.de
0x17.deanswers its DNS
MX
mail.0x17.de
0x17.dereceives its email
TLS
0x17.de
Let's Encryptissued its certificate

DNS Records

A 4

  • 144.76.237.30
  • 162.55.3.185
  • 176.9.219.86
  • 213.239.204.83

AAAA 4

  • 2a01:4f8:13a:2662::2
  • 2a01:4f8:201:1305::2
  • 2a01:4f8:222:ed8::2
  • 2a01:4f8:252:4ca::2

MX 1

  • 20mail.0x17.de

TXT 3

  • google-site-verification=NnuuDI6mKHJ2GNSg_mHXCTkOYUPqJB2B9KmEieadb-c
  • keybase-site-verification=ywqGW2W0KU0Z-UxYvPrRsVgluKXaZtyozS14xRoCBbk
  • v=spf1 a mx ip4:5.9.38.14 ip6:2a01:4f8:161:220c::2 ip4:162.55.3.185 ip6:2a01:4f8:252:4ca::2 ip4:176.9.219.86 ip6:2a01:4f8:13a:2662::2 ip4:144.76.237.30 ip6:2a01:4f8:201:1305::2 ip4:213.239.204.83 ip6:2a01:4f8:222:ed8::2 -all

NS 2

  • ns1.0x17.de
  • ns2.0x17.de

SOA 1

  • ns1.0x17.de hostmaster.0x17.de

CAA 5

  • iodef "mailto:caa@0x17.de"
  • issue "letsencrypt.org; validationmethods=dns-01; accounturi=https://acme-staging-v02.api.letsencrypt.org/acme/acct/5932045"
  • issue "letsencrypt.org; validationmethods=dns-01; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/33412104"
  • issuewild "letsencrypt.org; validationmethods=dns-01; accounturi=https://acme-staging-v02.api.letsencrypt.org/acme/acct/5932045"
  • issuewild "letsencrypt.org; validationmethods=dns-01; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/33412104"

MCP_RECORDS 1

  • google-site-verification=NnuuDI6mKHJ2GNSg_mHXCTkOYUPqJB2B9KmEieadb-c

DMARC_RECORDS 1

  • v=DMARC1; p=quarantine; rua=mailto:dmarc-it@0x17.de; ruf=mailto:dmarc-it@0x17.de;

BIMI_RECORDS 1

  • google-site-verification=NnuuDI6mKHJ2GNSg_mHXCTkOYUPqJB2B9KmEieadb-c

MTA_STS_RECORDS 1

  • v=STSv1; id=20190505013700

TLS Certificates (3)

Common NameIssuerExpires
0x17.de C=US, O=Let's Encrypt, CN=YR2 Sun, 11 Oct 2026 21:05:57 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (0)

None observed.

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_7d8ce012d16d68f8
Output Hash
ecfa083975ed258f6387485a8dc4cceb6b7f5c2d7219bc6c3899e7c9e2bc19aa
Signature
ed25519:89f63d6a370b54670b8824d2ca0a7771138e3779cda69acc615a30768ed5f02ee90413d1d3d2f3b3fd2060b1003a3d66733262285efefcc50c2957ed814a1102
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT47,014 material changesacross 45,065 domains · last 24h · +2,932 vs yesterdayROTATION57 domains moved DNS from magpiedns.com to koaladns.com, 54 moved backa rotation loop, not a migration · 24hNOW498 curated domains not reachablelast probe, steadySITE ERRORS36,552 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,539 sites429 rate-limit / 403 bot-block, a posture signal