sachtiz.com
Observed Aug 12, 2026, 04:17 UTC (6d ago). Every field below was attested with an Ed25519 signature at scan time.
sachtiz.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting sachtiz.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 sachtiz.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Let's Encrypt
Microsoft 365Steady. No change on record for sachtiz.com in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.
DNS Records
A 1
83.65.2.30
AAAA 1
2a02:8384:11:100::30
MX 1
10mx.mymagenta.business
TXT 2
v=spf1 a mx include:_spf.mymagenta.business ip4:80.109.253.0/24 ~allMS=84FC9653180EF2697D6FC77FF7EE81BB8122FAFB
NS 2
ns2.nameservice.atns1.nameservice.at
SOA 1
ns1.nameservice.at domainadmin2.magenta.at
MCP_RECORDS 2
v=spf1 a mx include:_spf.mymagenta.business ip4:80.109.253.0/24 ~allMS=84FC9653180EF2697D6FC77FF7EE81BB8122FAFB
DMARC_RECORDS 1
v=DMARC1; p=none;
BIMI_RECORDS 2
v=spf1 a mx include:_spf.mymagenta.business ip4:80.109.253.0/24 ~allMS=84FC9653180EF2697D6FC77FF7EE81BB8122FAFB
MTA_STS_RECORDS 2
v=spf1 a mx include:_spf.mymagenta.business ip4:80.109.253.0/24 ~allMS=84FC9653180EF2697D6FC77FF7EE81BB8122FAFB
TLS Certificates (4)
| Common Name | Issuer | Expires |
|---|---|---|
sachtiz.com |
C=US, O=Let's Encrypt, CN=YE2 | Sat, 24 Oct 2026 08:53:54 +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 (0)
None observed.
DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works
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 receiptEd25519 Receipt
- Receipt ID
rcpt_f8ea59ef80d874c6- Output Hash
a9575cfba41253eed1f2da54dcefc66449ba1f1d006fce6d74c1cad77483e51c- Signature
ed25519:1861e12a445f95107e98d06e9cfbbf77892a1eb23e6648599a9c2a1f5fe1cabb614cc744fd9f9102df030bba6682a2d0731253a46d5c60a3fe267901129e5d0e- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast