tk63.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`tk63.com`

DNSSEC	⚠️ Not signed
A	18.136.207.62^{🇸🇬 Amazon18.136.0.0/16 EC2 SIN prefix}
		PTR	`ec2-18-136-207-62.ap-southeast-1.compute.amazonaws.com`
NS	`ns309.dnsever.com` ⭐
		A	91.134.148.223^{🇫🇷 OVH91.134.0.0/16}
			PTR	`ns309.dnsever.com`
NS	`ns331.dnsever.com`
		A	15.235.2.107^{🇨🇦 OVH15.235.0.0/17 Hosting route}
			PTR	`ns331.dnsever.com`
NS	`ns346.dnsever.com`
		A	5.39.12.230^{🇫🇷 OVH5.39.0.0/17 ISP Paris, France}
			PTR	`ns346.dnsever.com`
NS	`ns369.dnsever.com`
		A	91.134.148.201^{🇫🇷 OVH91.134.0.0/16}
			PTR	`ns19.dnsever.com`
NS	`ns384.dnsever.com`
SOA	`ns309.dnsever.com`root@tk63.com serial=1752754317

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1786933734

Same first word

tk63.com

tk63.ru

Similar names

kt36.com

kt36.cn

36tk.cc

36tk.us

k63t.xyz

63kt.com

36kt.cn

36tk.com

kt36.df.gov.br

k36t.com

tk36.ru

DNS History

27 records (6 active, 21 former)

○NSdns1.iidns.com2016-08-31 → 2016-12-19 · 5 obs

○ 2016-03-03 14:38:54
● 2016-08-31 09:32:32
● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

○NSdns1.name-services.com2008-12-24 → 2008-12-24 · 3 obs

● 2008-12-24 03:03:16
○ 2015-06-24 19:48:24
○ 2026-08-17 02:35:00

○NSdns2.iidns.com2016-08-31 → 2016-12-19 · 5 obs

○ 2016-03-03 14:38:54
● 2016-08-31 09:32:32
● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

○NSdns2.name-services.com2008-12-24 → 2008-12-24 · 3 obs

● 2008-12-24 03:03:16
○ 2015-06-24 19:48:24
○ 2026-08-17 02:35:00

○NSdns3.iidns.com2016-08-31 → 2016-12-19 · 5 obs

○ 2016-03-03 14:38:54
● 2016-08-31 09:32:32
● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

○NSdns3.name-services.com2008-12-24 → 2008-12-24 · 3 obs

● 2008-12-24 03:03:16
○ 2015-06-24 19:48:24
○ 2026-08-17 02:35:00

○NSdns4.iidns.com2016-08-31 → 2016-12-19 · 5 obs

○ 2016-03-03 14:38:54
● 2016-08-31 09:32:32
● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

○NSdns4.name-services.com2008-12-24 → 2008-12-24 · 3 obs

● 2008-12-24 03:03:16
○ 2015-06-24 19:48:24
○ 2026-08-17 02:35:00

○NSdns5.iidns.com2016-08-31 → 2016-12-19 · 5 obs

○ 2016-03-03 14:38:54
● 2016-08-31 09:32:32
● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

○NSdns5.name-services.com2008-12-24 → 2008-12-24 · 3 obs

● 2008-12-24 03:03:16
○ 2015-06-24 19:48:24
○ 2026-08-17 02:35:00

○NSdns6.iidns.com2016-08-31 → 2016-12-19 · 5 obs

○ 2016-03-03 14:38:54
● 2016-08-31 09:32:32
● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

○NSns1.51dns.com2015-06-24 → 2016-03-03 · 5 obs

○ 2008-12-24 03:03:16
● 2015-06-24 19:48:24
● 2016-03-03 14:38:54
○ 2016-08-31 09:32:32
○ 2026-08-17 02:35:00

○NSns2.51dns.com2015-09-16 → 2016-03-03 · 5 obs

○ 2008-12-24 03:03:16
● 2015-09-16 19:54:24
● 2016-03-03 14:38:54
○ 2016-08-31 09:32:32
○ 2026-08-17 02:35:00

●NSns309.dnsever.com2017-12-02 → 2026-08-17 · 3 obs

○ 2016-12-19 10:04:50
● 2017-12-02 05:35:42
● 2026-08-17 02:35:00

●NSns331.dnsever.com2017-12-02 → 2026-08-17 · 3 obs

○ 2016-12-19 10:04:50
● 2017-12-02 05:35:42
● 2026-08-17 02:35:00

●NSns346.dnsever.com2017-12-02 → 2026-08-17 · 3 obs

○ 2016-12-19 10:04:50
● 2017-12-02 05:35:42
● 2026-08-17 02:35:00

●NSns369.dnsever.com2017-12-02 → 2026-08-17 · 3 obs

○ 2016-12-19 10:04:50
● 2017-12-02 05:35:42
● 2026-08-17 02:35:00

●NSns384.dnsever.com2017-12-02 → 2026-08-17 · 3 obs

○ 2016-12-19 10:04:50
● 2017-12-02 05:35:42
● 2026-08-17 02:35:00

○A104.160.182.1322016-12-19 → 2016-12-19 · 4 obs

○ 2016-07-13 12:58:10
● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

○A104.160.182.1352016-12-19 → 2016-12-19 · 4 obs

○ 2016-07-13 12:58:10
● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

○A104.37.244.2002016-06-10 → 2016-06-10 · 4 obs

○ 2016-03-03 14:38:54
● 2016-06-10 12:10:50
○ 2016-07-13 12:58:10
○ 2026-08-17 02:35:00

●A18.136.207.622026-06-14 → 2026-08-17 · 3 obs

○ 2017-12-02 05:35:42
● 2026-06-14 22:48:48
● 2026-08-17 02:35:00

○A206.161.216.502017-12-02 → 2017-12-02 · 4 obs

○ 2016-12-19 10:04:50
● 2017-12-02 05:35:42
○ 2026-06-14 22:48:48
○ 2026-08-17 02:35:00

○A43.250.50.1432015-06-24 → 2016-03-03 · 5 obs

○ 2008-12-24 03:03:16
● 2015-06-24 19:48:24
● 2016-03-03 14:38:54
○ 2016-06-10 12:10:50
○ 2026-08-17 02:35:00

○A47.88.33.672016-07-13 → 2016-07-13 · 4 obs

○ 2016-06-10 12:10:50
● 2016-07-13 12:58:10
○ 2016-12-19 10:04:50
○ 2026-08-17 02:35:00

○A69.64.155.1192008-12-24 → 2008-12-24 · 3 obs

● 2008-12-24 03:03:16
○ 2015-06-24 19:48:24
○ 2026-08-17 02:35:00

○CNAMEfw.ename.net2016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 10:04:50
○ 2017-12-02 05:35:42
○ 2026-08-17 02:35:00

🔍 DNS Trace

Analysis

IP Addresses

tk63.com resolves to one IP address: 18.136.207.62.

ec2-18-136-207-62.ap-southeast-1.compute.amazonaws.com, tk38.com, 00tk.com and two other host names share IP numbers with tk63.com.

Name Servers

tk63.com has five name servers, which are ns309.dnsever.com, ns331.dnsever.com, ns346.dnsever.com and two others.

At least some of tk63.com's name servers are shared with other domains, for example 3659337.cc, 16767711.com, enticket.com and two more.

These name servers tend to co-occur with ns384.dnsever.com, ns369.dnsever.com, ns322.dnsever.com and 7 other name servers in the same DNS delegations.

Each of the four hosts ns309.dnsever.com, ns331.dnsever.com, ns346.dnsever.com and ns369.dnsever.com points to a single IP address — ns309.dnsever.com points to 91.134.148.223, ns331.dnsever.com points to 15.235.2.107, ns346.dnsever.com points to 5.39.12.230 and ns369.dnsever.com points to 91.134.148.201.