`bykamy.com`

DNSSEC	⚠️ Not signed
A	209.126.31.101^{🇺🇸 NEXCESS-01209.126.16.0/20 209.126.16.0/20}
NS	`ns1.nexcess.net` ⭐
		A	2607:f7c0:8001::a^{🇺🇸 NEXCESS-012607:f7c0:8001::/48 Proxy route}
		A	192.240.188.188^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns2.nexcess.net`
		A	2607:f7c0:8002::a^{🇺🇸 NEXCESS-012607:f7c0:8002::/48 Proxy route}
		A	192.240.188.166^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns3.nexcess.net`
		A	2607:f7c0:8001::b^{🇺🇸 NEXCESS-012607:f7c0:8001::/48 Proxy route}
		A	192.240.188.144^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns4.nexcess.net`
		A	2607:f7c0:8002::b^{🇺🇸 NEXCESS-012607:f7c0:8002::/48 Proxy route}
		A	192.240.188.122^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns5.nexcess.net`
		A	2607:f7c0:8002::b^{🇺🇸 NEXCESS-012607:f7c0:8002::/48 Proxy route}
		A	192.240.188.122^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns6.nexcess.net`
		A	2607:f7c0:8001::b^{🇺🇸 NEXCESS-012607:f7c0:8001::/48 Proxy route}
		A	192.240.188.144^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns7.nexcess.net`
		A	2607:f7c0:8002::a^{🇺🇸 NEXCESS-012607:f7c0:8002::/48 Proxy route}
		A	192.240.188.166^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
NS	`ns8.nexcess.net`
		A	2607:f7c0:8001::a^{🇺🇸 NEXCESS-012607:f7c0:8001::/48 Proxy route}
		A	192.240.188.188^{🇺🇸 NEXCESS-01192.240.188.0/24 Customer route registered by AS63956}
MX	`bykamy-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::16^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr04cu00306.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00307.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mn2pr02cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:f90f::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr04cu00201.inbound.protection.outlook.com`
		A	52.101.9.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.11.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr03cu00102.inbound.protection.outlook.com`
		A	52.101.40.6^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy1pr03cu00106.inbound.protection.outlook.com`
		A	52.101.41.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr05cu00400.inbound.protection.outlook.com`
TXT	`sipfed.online.lync.com`
TXT	`v=spf1 include:spf1.auinmeio.com.br include:spf2.auinmeio.com.br a mx include...`
TXT	`sipdir.online.lync.com`
SOA	`ns1.nexcess.net`hostmaster@bykamy.com serial=1544636170

`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=1774502327

Same first word

bykamy.com.br

bykamy.com

DNS History

30 records (10 active, 20 former)

○NSdns1.kinghost.com.br2016-07-01 → 2017-03-27 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○NSdns2.kinghost.com.br2016-07-01 → 2017-03-27 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○NSdns3.kinghost.com.br2016-07-01 → 2017-03-27 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○NSdns4.kinghost.com.br2016-07-01 → 2017-03-27 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○NSdns5.kinghost.com.br2016-07-01 → 2017-03-27 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○NSdns6.kinghost.com.br2016-07-01 → 2017-03-27 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○NSns-1088.awsdns-08.org2015-07-11 → 2016-02-08 · 4 obs

● 2015-07-11 19:58:18
● 2016-02-08 03:59:04
○ 2016-07-01 17:19:54
○ 2026-03-26 05:35:44

○NSns-2043.awsdns-63.co.uk2015-07-11 → 2016-02-08 · 4 obs

● 2015-07-11 19:58:18
● 2016-02-08 03:59:04
○ 2016-07-01 17:19:54
○ 2026-03-26 05:35:44

○NSns-337.awsdns-42.com2015-07-11 → 2016-02-08 · 4 obs

● 2015-07-11 19:58:18
● 2016-02-08 03:59:04
○ 2016-07-01 17:19:54
○ 2026-03-26 05:35:44

○NSns-737.awsdns-28.net2015-07-11 → 2016-02-08 · 4 obs

● 2015-07-11 19:58:18
● 2016-02-08 03:59:04
○ 2016-07-01 17:19:54
○ 2026-03-26 05:35:44

●NSns1.nexcess.net2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

●NSns2.nexcess.net2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

●NSns3.nexcess.net2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

●NSns4.nexcess.net2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

●NSns5.nexcess.net2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

●NSns6.nexcess.net2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

●NSns7.nexcess.net2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

●NSns8.nexcess.net2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

○MXalt1.aspmx.l.google.com2015-07-11 → 2017-03-27 · 3 obs

● 2015-07-11 19:58:18
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○MXalt2.aspmx.l.google.com2015-07-11 → 2017-03-27 · 3 obs

● 2015-07-11 19:58:18
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○MXalt3.aspmx.l.google.com2016-07-01 → 2017-03-27 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○MXalt4.aspmx.l.google.com2016-07-01 → 2017-03-27 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○MXaspmx.l.google.com2015-07-11 → 2017-03-27 · 3 obs

● 2015-07-11 19:58:18
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○MXaspmx2.googlemail.com2015-07-11 → 2016-02-08 · 4 obs

● 2015-07-11 19:58:18
● 2016-02-08 03:59:04
○ 2016-07-01 17:19:54
○ 2026-03-26 05:35:44

○MXaspmx3.googlemail.com2015-07-11 → 2016-02-08 · 4 obs

● 2015-07-11 19:58:18
● 2016-02-08 03:59:04
○ 2016-07-01 17:19:54
○ 2026-03-26 05:35:44

●MXbykamy-com.mail.protection.outlook.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

○A177.185.192.1092016-07-01 → 2016-07-01 · 4 obs

○ 2016-02-08 03:59:04
● 2016-07-01 17:19:54
○ 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

○A177.185.192.1222017-03-27 → 2017-03-27 · 3 obs

○ 2016-07-01 17:19:54
● 2017-03-27 18:37:06
○ 2026-03-26 05:35:44

●A209.126.31.1012026-03-26 → 2026-03-26 · 2 obs

○ 2017-03-27 18:37:06
● 2026-03-26 05:35:44

○A54.213.11.1392015-07-11 → 2016-02-08 · 4 obs

● 2015-07-11 19:58:18
● 2016-02-08 03:59:04
○ 2016-07-01 17:19:54
○ 2026-03-26 05:35:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, c.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net...	-
bykamy.com	ns2.nexcess.net, ns1.nexcess.net, ns3.nexcess.net, ns4.nexcess.net...	-

✅ Authoritative Response

Server:192.240.188.166

NS records: ns2.nexcess.net, ns1.nexcess.net, ns3.nexcess.net, ns4.nexcess.net, ns5.nexcess.net, ns6.nexcess.net, ns7.nexcess.net, ns8.nexcess.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bykamy.com (unsigned zone)

⏱️ Timing

Total: 579ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`209.126.31.101`
NS	8	`ns3.nexcess.net, ns2.nexcess.net...`
MX	1	`bykamy-com.mail.protection.outlook.com (`
TXT	3	`sipfed.online.lync.com, v=spf1 include:spf1.auinmeio.com.br incl...`
SOA	1	`ns1.nexcess.net hostmaster.bykamy.com`

Analysis

IP Addresses

bykamy.com resolves to one IP number: 209.126.31.101.

Other host names for instance cloudhost-67022.us-midwest-1.nxcli.net and mail.bykamy.com.br share IP numbers with bykamy.com.

Name Servers

bykamy.com is delegated to eight name servers: ns1.nexcess.net, ns2.nexcess.net, ns3.nexcess.net, ns4.nexcess.net, ns5.nexcess.net, ns6.nexcess.net, ns7.nexcess.net and ns8.nexcess.net.

bykamy.com at least partially shares name servers with other domains, including greenairglobal.com, 7storm.org, gezategaru.com, embeddedartistry.com and 170.240.192.in-addr.arpa.

Two IP numbers per host:

ns1.nexcess.net points to 2607:f7c0:8001::a and 192.240.188.188

ns2.nexcess.net points to 2607:f7c0:8002::a and 192.240.188.166

ns3.nexcess.net points to 2607:f7c0:8001::b and 192.240.188.144

ns4.nexcess.net points to 2607:f7c0:8002::b and 192.240.188.122

ns5.nexcess.net points to 2607:f7c0:8002::b and 192.240.188.122

ns6.nexcess.net points to 2607:f7c0:8001::b and 192.240.188.144

ns7.nexcess.net points to 2607:f7c0:8002::a and 192.240.188.166

ns8.nexcess.net points to 2607:f7c0:8001::a and 192.240.188.188

Host names that point to 2607:f7c0:8001::a: ns1.nexcess.net and ns8.nexcess.net

Host names that point to 192.240.188.188: ns1.nexcess.net and ns8.nexcess.net

Host names that point to 2607:f7c0:8002::a: ns2.nexcess.net and ns7.nexcess.net

Host names that point to 192.240.188.166: ns2.nexcess.net and ns7.nexcess.net

Host names that point to 2607:f7c0:8001::b: ns3.nexcess.net and ns6.nexcess.net

Host names that point to 192.240.188.144: ns3.nexcess.net and ns6.nexcess.net

Host names that point to 2607:f7c0:8002::b: ns4.nexcess.net and ns5.nexcess.net

Host names that point to 192.240.188.122: ns4.nexcess.net and ns5.nexcess.net

Mail Servers

A single mail server handles bykamy.com, bykamy-com.mail.protection.outlook.com.

Host bykamy-com.mail.protection.outlook.com points to eight IPs: 2a01:111:f403:c902::16, 2a01:111:f403:c946::7, 2a01:111:f403:f902::2, 2a01:111:f403:f90f::1, 52.101.9.17, 52.101.11.2, 52.101.40.6 and 52.101.41.0.

bykamy.com - robtex.com

bykamy.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`bykamy.com`

`com`