remesas.org

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

This reading of remesas.org was taken 7d ago

remesas.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting remesas.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 remesas.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Registered withTUCOWS.COM, CO.
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for remesas.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 remesas.org actually stands on - every host below is a signed observation
remesas.org
A / AAAA
135.222.41.127
unattributedserves the site
NS
ns2.turbify.comns1.turbify.com
turbify.comanswers its DNS
MX
mx-biz.mail.am0.yahoodns.netmx-biz.mail.am0.yahoodns.net
yahoodns.netreceives its email

DNS Records

A 1

  • 135.222.41.127

MX 2

  • 30mx-biz.mail.am0.yahoodns.net
  • 20mx-biz.mail.am0.yahoodns.net

NS 2

  • ns2.turbify.com
  • ns1.turbify.com

SOA 1

  • ns1.turbify.com hostmaster.remesas.org

MCP_RECORDS 1

  • v=spf1 a mx ip4:135.222.41.127 include:relay.mailchannels.net -all

DMARC_RECORDS 1

  • v=spf1 a mx ip4:135.222.41.127 include:relay.mailchannels.net -all

BIMI_RECORDS 1

  • v=spf1 a mx ip4:135.222.41.127 include:relay.mailchannels.net -all

MTA_STS_RECORDS 1

  • v=spf1 a mx ip4:135.222.41.127 include:relay.mailchannels.net -all

TLS Certificates (0)

None.

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-17 16:49 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_c5cb9b3a930a66d4
Output Hash
93d7f7cce41c320b3ab98e8bcae2b640af59eb56ec8b22d070924e79f8a31d82
Signature
ed25519:991c17a8a2d31e01f50818d409710647aabb5a0502b19bce5e99119874325cbe4d30621bc0f2f2eb6596e1355380442fc3789da5f93f4cc84c4e007a3c7ea904
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT38,853 material changesacross 35,376 domains · 24h to ~50m ago · -2,398 vs yesterdayROTATION76 domains moved DNS from magpiedns.com to kirklanddc.com, 73 moved backa rotation loop, not a migration · 24hEMAIL DRIFT6 domains switched email provider24hNOW487 curated domains not reachablelast probe, steadySITE ERRORS33,769 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,234 sites429 rate-limit / 403 bot-block, a posture signal