Cause probable de la panne 3d Secure du 14 juin (vers 0840 UTC). L'historique récent du domaine, vu par DNSDB :
% isc-dnsdb-query rrset wlp-acs.com/NS
;; bailiwick: com.
;; count: 2597
;; first seen in zone file: 2010-04-24 16:12:21 -0000
;; last seen in zone file: 2017-06-14 16:02:38 -0000
wlp-acs.com. IN NS ns3.atos.net.
wlp-acs.com. IN NS ns4.atos.net.
;; bailiwick: com.
;; count: 514827
;; first seen: 2010-06-24 05:52:49 -0000
;; last seen: 2017-06-15 04:37:49 -0000
wlp-acs.com. IN NS ns3.atos.net.
wlp-acs.com. IN NS ns4.atos.net.
;; bailiwick: com.
;; count: 14
;; first seen: 2017-06-14 08:36:04 -0000
;; last seen: 2017-06-14 09:48:42 -0000
wlp-acs.com. IN NS sk.s5.ans1.ns148.ztomy.com.
wlp-acs.com. IN NS sk.s5.ans2.ns148.ztomy.com.
;; bailiwick: wlp-acs.com.
;; count: 830396
;; first seen: 2010-06-24 05:52:49 -0000
;; last seen: 2017-06-15 03:59:47 -0000
wlp-acs.com. IN NS ns3.atos.net.
wlp-acs.com. IN NS ns4.atos.net.
;; bailiwick: wlp-acs.com.
;; count: 5
;; first seen: 2017-06-14 08:42:35 -0000
;; last seen: 2017-06-14 10:12:31 -0000
wlp-acs.com. IN NS sk.s5.ans1.ns148.ztomy.com.
wlp-acs.com. IN NS sk.s5.ans2.ns148.ztomy.com.
;;; Returned 5 RRsets in 0.14 seconds.
;;; DNSDB
Après la remise en place du domaine