time.dnsp.co
The server clock, encoded as an address.
What it does
time.dnsp.co gives the hour, minute and second we answered, in the server's own timezone. time24.dnsp.co is the same value stated explicitly in 24 hour notation, time12.dnsp.co uses 12 hour notation, and date.dnsp.co gives yy.mm.dd.hh. Comparing against your own clock shows how long the answer has been sitting somewhere.
The server clock and your computer's clock are very likely in different time zones, so expect a whole number of hours between them. Note that offset once, then watch for the minutes and seconds drifting: that part is the age of the answer, not geography.
Example
$ dig @dnsp.co time.dnsp.co +short
14.32.07.0
$ dig @dnsp.co date.dnsp.co +short
26.09.14.14
Reading the answer
roughly the current time
The answer is live.
a time in the past
You are reading a cached record, and the gap is its age.
an unchanging value
Something is holding the record well past its lifetime.
Notes
- The server timezone is not yours. Subtract the fixed hourly offset before reading anything into the result.
- Half-hour and 45 minute zones exist, so check the minutes too when you first work out the offset.
- Only the drift matters, not the absolute value.