married-dating.org

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

This reading of married-dating.org was taken 6d ago

married-dating.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting married-dating.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 married-dating.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Secured byGoogle Trust Services
Also usesGoogle Search Console
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat married-dating.org actually stands on - every host below is a signed observation
married-dating.org
A / AAAA
104.21.6.173172.67.135.172606:4700:3035::6815:6ad2606:4700:3030::ac43:8711
Cloudflareserves the site
NS
dana.ns.cloudflare.competer.ns.cloudflare.com
cloudflare.comanswers its DNS
TLS
married-dating.org
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 104.21.6.173
  • 172.67.135.17

AAAA 2

  • 2606:4700:3035::6815:6ad
  • 2606:4700:3030::ac43:8711

TXT 2

  • google-site-verification=rtQMbbJQoTpTVHjaUW0VEZNOgy11IdkCSyBcQDnG3BY
  • v=spf1 -all

NS 2

  • dana.ns.cloudflare.com
  • peter.ns.cloudflare.com

SOA 1

  • dana.ns.cloudflare.com dns.cloudflare.com

DMARC_RECORDS 1

  • v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s;

TLS Certificates (3)

Common NameIssuerExpires
married-dating.org C=US, O=Google Trust Services, CN=WE1 Mon, 21 Sep 2026 11:29:31 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (0)

None observed.

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_ae60547786feedbc
Output Hash
7d25d0ea7eba624dad77ad05bf8202f47464ca3f787b90c10522adf03fa37589
Signature
ed25519:636f1eb3c0fdcc9445e18e2a0f60c748592c91887ed0e2ee2da6b5fe5cff3a23ae28d5d9f612893b0031285ab5c74614ddbd3c1ae3e9a9d799cc9543a2748c0b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT39,303 material changesacross 37,396 domains · 24h to ~2h ago · -2,256 vs yesterdayROTATION67 domains moved DNS from magpiedns.com to koaladns.com, 62 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW589 curated domains not reachable+94 vs yesterdaySITE ERRORS36,075 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,370 sites429 rate-limit / 403 bot-block, a posture signal