CONTINUOUS INTERNET TELEMETRY24H DRIFT3,609 material changesacross 3,128 domains · +211 vs yesterdayDNS DRIFT26 domains changed DNS providertop destination digicertdns.com + digicertdns.net · -1 vs yesterdayEMAIL DRIFT6 domains switched email providertop destination sendgw.comCERT DRIFT9 domains switched issuing CA24h · +2 vs yesterdayNOW3,326 curated domains not answering-6,392 vs yesterdayERRORS10,955 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,609 material changesacross 3,128 domains · +211 vs yesterdayDNS DRIFT26 domains changed DNS providertop destination digicertdns.com + digicertdns.net · -1 vs yesterdayEMAIL DRIFT6 domains switched email providertop destination sendgw.comCERT DRIFT9 domains switched issuing CA24h · +2 vs yesterdayNOW3,326 curated domains not answering-6,392 vs yesterdayERRORS10,955 responded with an errorlast probe · 5xx / 404 / 429 / 403

reply.com

Observed 2026-07-12T17:22:19.750Z (10h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Also usesAtlassianGoogle Search ConsoleHubSpot
9 subdomains · consulting
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat reply.com actually stands on - every host below is a signed observation
reply.com
A / AAAA
54.246.157.8699.80.3.188
Cloudflareserves the site
NS
dns4.reply.itdns1.reply.itdns2.reply.it
reply.itanswers its DNS
MX
reply-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.reply.com:443/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time1003 ms
DNS resolutionNOERROR
Redirect chain
https://www.reply.com:443/

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 2

  • 54.246.157.86
  • 99.80.3.188

MX 1

  • 5reply-com.mail.protection.outlook.com

TXT 29

  • duo_sso_verification=LmQ7ptX7Z9m11sxpljtrdu3EuIS4mTyRyDoY3wXEUC2w0ZiIkkekE31mAKSbRQss
  • atlassian-domain-verification=tom8ff8aw3rXiFqYnUEQaaiNRc9y884zvefZnAACy0sqliefMa8F30oEbNGwp1W1
  • google-site-verification=sIyfK--Jw6BqzuUXnkYBV2Ppz7W_QqCgVFaXYxyrV1c
  • google-site-verification=5r1_bF5mpy_4ek9DPOcebqALnwu49JapnS2qhH9f4h8
  • beaiqbj3r93pl70v68lpjdmofr
  • google-site-verification=HErK3TnMluADktS9nHQjSKcQsKOG2Sg3k3_yDPp9M30
  • hubspot-HE0fT930qJle
  • atlassian-domain-verification=dw4fi0qCEKJUZyelAkmK1vrXVIwUqAFwuI5yaQ4tyP2TYaKtvdnhfOBieTqLEl/B
  • qZQc/C3ASDzTUyuV52uNT9wHNBXcKrs5x4ZfoFOfALs29qfF598COORULoNPd1dRcbT/vuVcBoFm/QUuK1+H9g==
  • c609hq7g9jeqd95nplhccbegd0

NS 3

  • dns4.reply.it
  • dns1.reply.it
  • dns2.reply.it

SOA 1

  • dns1.reply.it administrator.reply.it

TLS Certificates (0)

None.

Subdomains (9)

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; nothing leaves your machine.

Verify this receipt

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for reply.com. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for reply.com <a href="https://domaindrift.io/t/reply.com"> <img src="https://domaindrift.io/badge/reply.com.svg" width="300" height="64" alt="DomainDrift signed observations for reply.com"> </a>

Ed25519 Receipt

Receipt ID
ae1b944b-5b40-45d3-a041-8022b5ad483b
Output Hash
0472f941397ec31cc5c3504235f35f19f2c2fbdafa40d95c22f0caa71741f44a
Signature
ed25519:2e1f14001dd0c08563ef3076527e95620912fb4861ad431546b2b8149ced3742e3a60653ad42f75830b88d7a8011bb77c77b6c0551571034d5740525b38c200e
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser