Isolated experiment

DNS / TLS lab

Measure which destination addresses and TLS sessions survive a cookie clear or network change. IDs on this page belong only to this lab.

Run a visit

Loading lab settings…

Use the same case on both devices. The device label is excluded from identity decisions. Clearing the lab cookie leaves TLS and DNS state alone. Every verify response closes its connection so a later visit measures a new handshake.

Case link

Latest observation

No visit yet.

Full observation 
{}

Visit history

Results stay in this tab until you export them.

Cookie clear + Wi-Fi switch

  1. Run a baseline visit.
  2. Clear the lab cookie.
  3. Change Wi-Fi, keep this tab open, and wait for connectivity.
  4. Run another visit. Compare the lab ID, TLS session and both destination addresses.

A changed DNS answer is an observation, not a test failure by itself. This lab does not classify a network switch as bot activity.

Shared-network collision

  1. Open the same case link on two devices using the same network.
  2. Give them different note labels and run a visit on each.
  3. Clear each lab cookie and repeat.
  4. Check whether equal DNS destinations still produce separate recognized TLS identities.

A public resolver may reorder or share its cached answers. The server's answer order does not prove the device's selection order.

Lab controls and server observations

These controls need the lab access key. Settings affect future authoritative answers; existing DNS caches may retain earlier answers. Closing lab connections keeps DNS settings, TLS sessions and lab identities available for the next visit. 


    

    

      The two lab page origins share a registrable domain. This is not a claim
      of cross-site cache continuity. Lab identity maps reset when the service
      restarts; compare the epoch in exported results.