managingpartnerforum.org

Observed Aug 9, 2026, 19:19 UTC (8d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of managingpartnerforum.org was taken 8d ago

managingpartnerforum.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting managingpartnerforum.org 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 managingpartnerforum.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Email byMicrosoft 365
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for managingpartnerforum.org 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.

INFRASTRUCTURE MAPwhat managingpartnerforum.org actually stands on - every host below is a signed observation
managingpartnerforum.org
A / AAAA
35.85.109.184
unattributedserves the site
NS
ns1.worldnic.comns2.worldnic.com
worldnic.comanswers its DNS
MX
managingpartnerforum-org.mail.protection.outlook.com
Microsoft 365receives its email

DNS Records

A 1

  • 35.85.109.184

MX 1

  • 10managingpartnerforum-org.mail.protection.outlook.com

TXT 3

  • MS=ms42632532
  • nh84bt52k6nh52lc0186dgivg5
  • v=spf1 include:spf.protection.outlook.com -all

NS 2

  • ns1.worldnic.com
  • ns2.worldnic.com

SOA 1

  • NS1.WORLDNIC.COM namehost.WORLDNIC.COM

MCP_RECORDS 1

  • v=spf1 a mx ip4:64.78.151.128/26 ip4:216.241.183.0/24 ~all

DMARC_RECORDS 1

  • v=spf1 a mx ip4:64.78.151.128/26 ip4:216.241.183.0/24 ~all

BIMI_RECORDS 1

  • v=spf1 a mx ip4:64.78.151.128/26 ip4:216.241.183.0/24 ~all

MTA_STS_RECORDS 1

  • v=spf1 a mx ip4:64.78.151.128/26 ip4:216.241.183.0/24 ~all

TLS Certificates (0)

None.

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-15 18:42 UTC

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

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_de3c479dd46a1448
Output Hash
f4359846ab1554ba7d0d7e5eed06a09a05a646fc76c4f9ea03e3d4b272f1c4f9
Signature
ed25519:6497ee1f595e2ef07727842d50f76669bfff2fc7384b262446702973ce7e43f9f400bda31b178b5d17e4a29600a3e9c1d2128da42b668263e01b0d733ea98301
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT40,911 material changesacross 38,996 domains · 24h to ~65m ago · +1,671 vs yesterdayROTATION62 domains moved DNS from koaladns.com to magpiedns.com, 61 moved backa rotation loop, not a migration · 24hEMAIL DRIFT4 domains switched email providertop destination alltheemails.comNOW540 curated domains not reachable-51 vs yesterdaySITE ERRORS34,284 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,612 sites429 rate-limit / 403 bot-block, a posture signal