juren.com

Observed Aug 16, 2026, 06:56 UTC (17h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Up right now
Secured byGoDaddy.com
Registered withHefei Juming Network Technology Co., Ltd.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

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

INFRASTRUCTURE MAPwhat juren.com actually stands on - every host below is a signed observation
juren.com
A / AAAA
76.223.54.14613.248.169.48
unattributedserves the site
NS
ns1.afternic.comns2.afternic.com
afternic.comanswers its DNS
TLS
juren.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 76.223.54.146
  • 13.248.169.48

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns1.afternic.com
  • ns2.afternic.com

SOA 1

  • ns2.afternic.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (4)

Common NameIssuerExpires
juren.com C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1 Wed, 10 Feb 2027 13:27:38 +0000
GoDaddy TLS Intermediate CA DV - R1v1 C=US, O=GoDaddy.com, CN=GoDaddy TLS Root CA - R1 Fri, 24 Aug 2040 11:59:59 +0000
GoDaddy TLS Root CA - R1 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000
Go Daddy Root Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-16 06:56 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, and what it shows

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_c89a1c3ba5055f34
Output Hash
6c1a3bc20aa864677a6d554231b4506c8b8224432481689e77edab93c012e2bb
Signature
ed25519:894b667c7fad5475a74ac07d4bb09c405a27c86a12ab29a40de28d35b677d5117edc50efc60d7ced34d6fa103b76a9e34adc45cf0c7c2256ffd63070ce04ec0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT39,240 material changesacross 37,425 domains · 24h to ~3h agoROTATION59 domains moved DNS from koaladns.com to magpiedns.com, 58 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW591 curated domains not reachablelast probe, steadySITE ERRORS35,522 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,252 sites429 rate-limit / 403 bot-block, a posture signal