A-record propagation for 'ns8.googledomains.com'


Authoritative name servers

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

Global name servers

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

North America

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

South America

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

Europe

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

Africa

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

Asia

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

Oceania

VOCPhone
Sydney, Australia
A
216.239.38.10
Telstra
Melbourne, Australia
A
216.239.38.10

Log

+002
  • Find SOA and NS records of 'ns8.googledomains.com'
+002
  • Query the autoritative nameservers for SOA and NS records of 'ns8.googledomains.com'
+139
  • Got response from ns5.googledomains.com.
+139
  • Add SOA server to check
+139
  • Nameserver responsibile of SOA records added: ns5.googledomains.com
+139
  • Query the SOA-server for NS records of 'googledomains.com'
+167
  • Got response from ns5.googledomains.com.
+167
  • Add NS servers to check
+167
  • Secondary nameserver added: ns6.googledomains.com
+167
  • Secondary nameserver added: ns7.googledomains.com
+167
  • Secondary nameserver added: ns8.googledomains.com
+167
  • Checking nameservers
+217
  • Google DNS checked in 19 ms.
+218
  • Open DNS checked in 20 ms.
+218
  • WideOpenWest checked in 18 ms.
+220
  • Secondary nameserver (ns8.googledomains.com) checked in 24 ms.
+222
  • UltraDNS checked in 25 ms.
+222
  • Secondary nameserver (ns6.googledomains.com) checked in 28 ms.
+225
  • Secondary nameserver (ns7.googledomains.com) checked in 29 ms.
+226
  • Telumasp checked in 25 ms.
+227
  • Alibaba checked in 31 ms.
+229
  • Level 3 Communications Inc checked in 29 ms.
+232
  • AdGuard checked in 30 ms.
+233
  • Cloudflare checked in 34 ms.
+264
  • Gcore checked in 67 ms.
+269
  • Freenom World checked in 72 ms.
+272
  • Radiant checked in 72 ms.
+299
  • Quad9 checked in 99 ms.
+303
  • dns0.eu checked in 102 ms.
+316
  • British Telecommunications checked in 119 ms.
+342
  • dnsforge.de checked in 143 ms.
+343
  • Telefonica Servicios Internet checked in 147 ms.
+350
  • nifty.com checked in 148 ms.
+356
  • Yandex checked in 159 ms.
+382
  • IRIDEOS checked in 182 ms.
+389
  • DynDNS checked in 195 ms.
+413
  • China Mobile checked in 217 ms.
+431
  • VOCPhone checked in 235 ms.
+436
  • Milcom Co Ltd checked in 234 ms.
+436
  • hk.net checked in 236 ms.
+457
  • TeamCAD checked in 259 ms.
+481
  • Telstra checked in 284 ms.
+527
  • Nigerian Communications Satellite Ltd checked in 331 ms.
+676
  • Global Network Systems checked in 482 ms.
+747
  • Maharashtra gov checked in 548 ms.
+2.202
  • Check of Interonda failed in 2.008ms: ConnectionTimeout
+2.202
  • Check of BlissDNS failed in 2.003ms: 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 .