bluhmsysteme.com

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

This reading of bluhmsysteme.com was taken 4d ago

bluhmsysteme.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bluhmsysteme.com 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 bluhmsysteme.com 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 ConsoleAppleFacebook/MetaMicrosoft 365SpyCloud
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-14 14:21 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 bluhmsysteme.com actually stands on - every host below is a signed observation
bluhmsysteme.com
A / AAAA
145.253.155.220
unattributedserves the site
NS
ns27.domaincontrol.comns28.domaincontrol.com
domaincontrol.comanswers its DNS
MX
mail.bluhmsysteme.com
bluhmsysteme.comreceives its email
TLS
bluhmsysteme.ch
Let's Encryptissued its certificate

DNS Records

A 1

  • 145.253.155.220

MX 1

  • 10mail.bluhmsysteme.com

TXT 10

  • google-site-verification=Qj5Le-A_YFF1rjWLw0aLnIjeiFc9IhfCVr13N8fSQ08
  • asv=47bd8fe38460ecf976c740381190c253
  • apple-domain-verification=6AbU-Z3B38ue8XWyFUALM3Nt6FXcM60U-lEpGAiV6JQ
  • facebook-domain-verification=qemfjtqojrhn909eqgg70ierivn4mz
  • v=spf1 mx include:spf.protection.outlook.com include:ispgateway.de include:spfa.cpmails.com ip4:80.146.186.162 ip4:80.146.186.166 ip4:185.16.114.200 -all
  • google-site-verification=DiVMruzyylmNXBxYmxdFOSZiYRSvaRdCVoei4ZAjcAw
  • eq568eslvsnvclvj9cgioqrjod
  • MS=477B9CDC2744F86DF2EECBBC6B205213E0147F17
  • MS=ms29559516
  • spycloud-domain-verification=79046d54-3d52-4c62-9beb-984463b192b9

NS 2

  • ns27.domaincontrol.com
  • ns28.domaincontrol.com

SOA 1

  • ns27.domaincontrol.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 mx include:spf.protection.outlook.com include:ispgateway.de include:spfa.cpmails.com ip4:80.146.186.162 ip4:80.146.186.166 ip4:185.16.114.200 -all

DMARC_RECORDS 1

  • v=DMARC1; p=none;

BIMI_RECORDS 1

  • v=spf1 mx include:spf.protection.outlook.com include:ispgateway.de include:spfa.cpmails.com ip4:80.146.186.162 ip4:80.146.186.166 ip4:185.16.114.200 -all

MTA_STS_RECORDS 1

  • v=spf1 mx include:spf.protection.outlook.com include:ispgateway.de include:spfa.cpmails.com ip4:80.146.186.162 ip4:80.146.186.166 ip4:185.16.114.200 -all

TLS Certificates (4)

Common NameIssuerExpires
bluhmsysteme.ch C=US, O=Let's Encrypt, CN=YE2 Mon, 19 Oct 2026 14:03:55 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (1)

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_8e71130ef3a37c77
Output Hash
1a61abdcc044683c1d2c240e9a492c7407b95530521ad184275eadc9e3593352
Signature
ed25519:41d12268d0bde3ebee5e82e590d0b16fee8eb0dea3d686c02ac2a731525c74c4fb029b3e70e7f4337abe6fe91840db73ffa7e10c359cd2a9617759159320330d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT43,037 material changesacross 41,485 domains · 24h to ~40m ago · -470 vs yesterdayROTATION64 domains moved DNS from magpiedns.com to koaladns.com, 58 moved backa rotation loop, not a migration · 24hNOW495 curated domains not reachablelast probe, steadySITE ERRORS36,302 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,411 sites429 rate-limit / 403 bot-block, a posture signal