A-record propagation for 'ns-cloud-c2.googledomains.com'


Authoritative name servers

Primary nameserver (SOA)
ns5.googledomains.com
A
216.239.34.108
Secondary nameserver
ns6.googledomains.com
A
216.239.34.108
Secondary nameserver
ns7.googledomains.com
A
216.239.34.108
Secondary nameserver
ns8.googledomains.com
A
216.239.34.108

Global name servers

Google DNS
Mountain View, California, USA
A
216.239.34.108
Open DNS
San Francisco, California, USA
A
216.239.34.108
Cloudflare
Los Angeles, California, USA
A
216.239.34.108
Level 3 Communications Inc
Dallas, Texas, USA
A
216.239.34.108
Quad9
Berkeley, California, USA
A
216.239.34.108
DynDNS
Manchester, New Hampshire, United States
A
216.239.34.108
Alibaba
Hangzhou, China
A
216.239.34.108
Gcore
Luxembourg
A
216.239.34.108
UltraDNS
Washington D.C., USA
A
216.239.34.108

North America

BlissDNS
Richardson, Texas, USA
ConnectionTimeout
WideOpenWest
Indiana, USA
A
216.239.34.108
Radiant
Vancouver, Canada
A
216.239.34.108
Telumasp
Monterrey, Mexico
A
216.239.34.108

South America

Interonda
Puerto Ibicuy, Argentina
ConnectionTimeout
Telefonica Servicios Internet
Lima, Peru
A
216.239.34.108

Europe

British Telecommunications
Ipswich, United Kingdom
A
216.239.34.108
Freenom World
Netherlands
A
216.239.34.108
dnsforge.de
Germany
A
216.239.34.108
IRIDEOS
Milan, Italy
A
216.239.34.108
AdGuard
Limassol, Cyprus
A
216.239.34.108
dns0.eu
France
A
216.239.34.108

Africa

Global Network Systems
Johannesburg, South Africa
A
216.239.34.108
Nigerian Communications Satellite Ltd
Nigeria
A
216.239.34.108

Asia

Yandex
Moscow, Russian Federation
A
216.239.34.108
TeamCAD
Petah Tikva, Israel
A
216.239.34.108
Maharashtra gov
Delhi, India
A
216.239.34.108
hk.net
Hong Kong
A
216.239.34.108
nifty.com
Tokyo, Japan
A
216.239.34.108
Milcom Co Ltd
Thailand
A
216.239.34.108
China Mobile
Beijing, China
A
216.239.34.108

Oceania

VOCPhone
Sydney, Australia
A
216.239.34.108
Telstra
Melbourne, Australia
A
216.239.34.108

Log

+003
  • Find SOA and NS records of 'ns-cloud-c2.googledomains.com'
+003
  • Query the autoritative nameservers for SOA and NS records of 'ns-cloud-c2.googledomains.com'
+122
  • Got response from ns6.googledomains.com.
+122
  • Add SOA server to check
+122
  • Nameserver responsibile of SOA records added: ns5.googledomains.com
+122
  • Query the SOA-server for NS records of 'googledomains.com'
+148
  • Got response from ns5.googledomains.com.
+148
  • Add NS servers to check
+148
  • Secondary nameserver added: ns6.googledomains.com
+148
  • Secondary nameserver added: ns7.googledomains.com
+148
  • Secondary nameserver added: ns8.googledomains.com
+148
  • Checking nameservers
+186
  • Open DNS checked in 7 ms.
+186
  • Level 3 Communications Inc checked in 6 ms.
+187
  • Cloudflare checked in 8 ms.
+195
  • Google DNS checked in 17 ms.
+199
  • WideOpenWest checked in 18 ms.
+201
  • Secondary nameserver (ns8.googledomains.com) checked in 24 ms.
+201
  • UltraDNS checked in 23 ms.
+202
  • Secondary nameserver (ns6.googledomains.com) checked in 28 ms.
+205
  • Secondary nameserver (ns7.googledomains.com) checked in 30 ms.
+207
  • Alibaba checked in 32 ms.
+212
  • DynDNS checked in 37 ms.
+214
  • Gcore checked in 37 ms.
+228
  • Quad9 checked in 47 ms.
+244
  • Radiant checked in 63 ms.
+276
  • Freenom World checked in 98 ms.
+281
  • British Telecommunications checked in 104 ms.
+284
  • dns0.eu checked in 101 ms.
+295
  • Telefonica Servicios Internet checked in 119 ms.
+303
  • dnsforge.de checked in 123 ms.
+304
  • IRIDEOS checked in 122 ms.
+315
  • AdGuard checked in 133 ms.
+327
  • nifty.com checked in 144 ms.
+328
  • TeamCAD checked in 149 ms.
+333
  • Yandex checked in 155 ms.
+368
  • Telstra checked in 190 ms.
+372
  • Telumasp checked in 190 ms.
+400
  • VOCPhone checked in 224 ms.
+400
  • China Mobile checked in 225 ms.
+407
  • hk.net checked in 225 ms.
+427
  • Milcom Co Ltd checked in 244 ms.
+433
  • Global Network Systems checked in 258 ms.
+440
  • Maharashtra gov checked in 259 ms.
+503
  • Nigerian Communications Satellite Ltd checked in 326 ms.
+2.180
  • Check of BlissDNS failed in 2.001ms: ConnectionTimeout
+2.180
  • Check of Interonda failed in 2.006ms: ConnectionTimeout
New features inbound 🚀
Within a couple of weeks, I'll launch a couple of new awesome features. Signup for the newsletter to stay updated, and get early access as a beta tester.

Signup using Google, Microsoft or Facebook .