dogcon.com - dns.ninja

dogcon.com

DNSSEC⚠️ Not signed
NSns1.google.com ⚠️ Not in zone NS records
A2001:4860:4802:32::a🇺🇸 Google2001:4860::/32
PTRns1.google.com
A216.239.32.10🇺🇸 Google216.239.32.0/24
PTRns1.google.com
NSns2.google.com ⚠️ Not in zone NS records
A2001:4860:4802:34::a🇺🇸 Google2001:4860::/32
PTRns2.google.com
A216.239.34.10🇺🇸 Google216.239.34.0/24
PTRns2.google.com

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1785692117

Same first word

dogcon.com

Similar names

cngood.net
cngodo.com
dognco.com
condog.net
cdngoo.com
goocdn.com
godcon.net
codong.net
cndgoo.com
dongco.com
codong.com
goodnc.co.kr
cogdon.org
cognod.com
dongco.com.vn
docngo.com
cngood.com.cn
congdo.com
godcon.org
gcondo.com
condog.com
dongco.net
dogocn.com

DNS History

19 records (2 active, 17 former)

20162017201820192020202120222023202420252026NSns1.google.comns2.google.comdns1.name-services.comdns1.registrar-servers.comdns2.name-services.comdns2.registrar-servers.comdns3.name-services.comdns3.registrar-servers.comdns4.name-services.comdns4.registrar-servers.comdns5.name-services.comdns5.registrar-servers.comMXeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.comA162.255.119.14269.64.147.243
○NSdns1.name-services.com2016-12-05 → 2017-05-15 · 5 obs
○ 2016-04-16 23:50:16
● 2016-12-05 18:21:50
● 2017-05-15 00:48:08
○ 2026-06-26 10:38:46
○ 2026-08-02 17:39:56
○NSdns1.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○NSdns2.name-services.com2016-12-05 → 2017-05-15 · 5 obs
○ 2016-04-16 23:50:16
● 2016-12-05 18:21:50
● 2017-05-15 00:48:08
○ 2026-06-26 10:38:46
○ 2026-08-02 17:39:56
○NSdns2.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○NSdns3.name-services.com2016-12-05 → 2017-05-15 · 5 obs
○ 2016-04-16 23:50:16
● 2016-12-05 18:21:50
● 2017-05-15 00:48:08
○ 2026-06-26 10:38:46
○ 2026-08-02 17:39:56
○NSdns3.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○NSdns4.name-services.com2016-12-05 → 2017-05-15 · 5 obs
○ 2016-04-16 23:50:16
● 2016-12-05 18:21:50
● 2017-05-15 00:48:08
○ 2026-06-26 10:38:46
○ 2026-08-02 17:39:56
○NSdns4.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○NSdns5.name-services.com2016-12-05 → 2017-05-15 · 5 obs
○ 2016-04-16 23:50:16
● 2016-12-05 18:21:50
● 2017-05-15 00:48:08
○ 2026-06-26 10:38:46
○ 2026-08-02 17:39:56
○NSdns5.registrar-servers.com2015-11-04 → 2016-01-23 · 5 obs
○ 2015-06-03 09:52:36
● 2015-11-04 16:50:14
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
●NSns1.google.com2026-06-26 → 2026-08-02 · 3 obs
○ 2017-05-15 00:48:08
● 2026-06-26 10:38:46
● 2026-08-02 17:39:56
●NSns2.google.com2026-06-26 → 2026-08-02 · 3 obs
○ 2017-05-15 00:48:08
● 2026-06-26 10:38:46
● 2026-08-02 17:39:56
○MXeforward1.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○MXeforward2.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○MXeforward3.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○MXeforward4.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○MXeforward5.registrar-servers.com2015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○A162.255.119.1422015-06-03 → 2016-01-23 · 4 obs
● 2015-06-03 09:52:36
● 2016-01-23 15:21:42
○ 2016-04-16 23:50:16
○ 2026-08-02 17:39:56
○A69.64.147.2432016-12-05 → 2017-05-15 · 5 obs
○ 2016-04-16 23:50:16
● 2016-12-05 18:21:50
● 2017-05-15 00:48:08
○ 2026-06-26 10:38:46
○ 2026-08-02 17:39:56

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
dogcon.comns2.google.com, ns1.google.com4 records

✅ Authoritative Response

Server:216.239.32.10

NS records: ns2.google.com, ns1.google.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dogcon.com (unsigned zone)

⏱️ Timing

Total: 123ms | Queries: -

📄 Records

TypeCountSample Data

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns2.google.com, ns2.google.com, ns1.google.com...)

Analysis

Name Servers

dogcon.com uses two name servers for its delegation: ns1.google.com and ns2.google.com.

dogcon.com has the same name server delegation as a number of other domains, such as ncicu.net, solanamobile-claim.live, publicbt.com and two more.

dogcon.com has at least partial name server overlap with other domains, such as adwords.jp, google.com.pg, bookrightregistry.org and two others.

It is common to see these name servers used together with name servers ns3.google.com and ns4.google.com.

The two host names ns1.google.com and ns2.google.com each have a pair of IP addresses: ns1.google.com has 216.239.32.10 and 2001:4860:4802:32::a, and ns2.google.com has 216.239.34.10 and 2001:4860:4802:34::a.