[ ric->~ ]$ dig @d.ns.se NS checkpoints.moneropulse.se
; <<>> DiG 9.10.0-P2 <<>> @d.ns.se NS checkpoints.moneropulse.se
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27487
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;checkpoints.moneropulse.se. IN NS
;; AUTHORITY SECTION:
moneropulse.se. 86400 IN NS is-it-true.moneropulse.se.
moneropulse.se. 86400 IN NS timewarp-again.moneropulse.se.
;; ADDITIONAL SECTION:
is-it-true.moneropulse.se. 86400 IN A 216.69.185.52
timewarp-again.moneropulse.se. 86400 IN A 208.109.255.52
;; Query time: 226 msec
;; SERVER: 81.228.8.16#53(81.228.8.16)
;; WHEN: Mon Apr 20 16:14:18 SAST 2015
;; MSG SIZE rcvd: 141
well now its not an easter egg anymore
NOOB ALERT: If you don't know what moneropulse is, its some sort of checkpoint feature that seems to have been added in response to the block 20-something something attack.
https://bitcointalk.org/index.php?topic=583449.msg9109547;topicseen#msg9109547
I didn't know what it was till I googled it. Hooray google.
I think it was more precisely developed "against" the BCX alledged exploits. Thus the "timewarp-again.moneropulse.se."