connect-api.com - dns.ninja

`connect-api.com`

DNSSEC	⚠️ Not signed
A	89.108.75.66^{🇷🇺 AS-REGRU89.108.75.0/24 Reg.Ru-B2C}
		PTR	`d53966.azlk.regrucolo.ru`
NS	`ns1.linode.com` ⭐
		A	2600:14c0:6::2^{🇺🇸 Akamai2600:14c0:6::/48 Technologies}
			PTR	`c1-2.akashield.net`
		A	92.123.94.2^{🇳🇱 Akamai92.123.94.0/24 Technologies}
			PTR	`c1-2.akashield.net`
NS	`ns2.linode.com`
		A	2600:14c0:6::3^{🇺🇸 Akamai2600:14c0:6::/48 Technologies}
			PTR	`c1-3.akashield.net`
		A	92.123.94.3^{🇳🇱 Akamai92.123.94.0/24 Technologies}
			PTR	`c1-3.akashield.net`
NS	`ns3.linode.com`
		A	2600:14c0:7::3^{🇺🇸 Akamai2600:14c0:7::/48 Technologies}
			PTR	`c2-3.akashield.net`
		A	92.123.95.3^{🇳🇱 Akamai92.123.95.0/24 Technologies}
			PTR	`c2-3.akashield.net`
NS	`ns4.linode.com` ⚠️ Not in parent delegation
		A	2600:14c0:7::4^{🇺🇸 Akamai2600:14c0:7::/48 Technologies}
			PTR	`c2-4.akashield.net`
		A	92.123.95.4^{🇳🇱 Akamai92.123.95.0/24 Technologies}
			PTR	`c2-4.akashield.net`
NS	`ns5.linode.com` ⚠️ Not in parent delegation
		A	2600:14c0:7::2^{🇺🇸 Akamai2600:14c0:7::/48 Technologies}
			PTR	`c2-2.akashield.net`
		A	92.123.95.2^{🇳🇱 Akamai92.123.95.0/24 Technologies}
			PTR	`c2-2.akashield.net`
MX	`mx.yandex.net` ⭐
		A	2a02:6b8::311^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
		A	77.88.21.249^{🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
TXT	`v=spf1 redirect=_spf.yandex.net`
SOA	`ns1.linode.com`info@connect-api.com serial=2021000031

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

Same first word

connect-api.com

connect-api.land

Similar names

api-connect.net

api-connect.io

pcn-noticea.top

api-connect.xyz

DNS History

23 records (7 active, 16 former)

○NSa.ns36.de2015-11-18 → 2016-02-27 · 5 obs

○ 2015-07-22 20:01:14
● 2015-11-18 10:56:48
● 2016-02-27 17:40:28
○ 2016-06-19 21:30:56
○ 2026-06-24 06:38:48

○NSb.ns36.de2015-11-18 → 2016-02-27 · 5 obs

○ 2015-07-22 20:01:14
● 2015-11-18 10:56:48
● 2016-02-27 17:40:28
○ 2016-06-19 21:30:56
○ 2026-06-24 06:38:48

○NSns-de.1and1-dns.biz2015-07-22 → 2015-07-22 · 3 obs

● 2015-07-22 20:01:14
○ 2015-11-18 10:56:48
○ 2026-06-24 06:38:48

○NSns-de.1and1-dns.com2015-07-22 → 2015-07-22 · 3 obs

● 2015-07-22 20:01:14
○ 2015-11-18 10:56:48
○ 2026-06-24 06:38:48

○NSns-de.1and1-dns.de2015-07-22 → 2015-07-22 · 3 obs

● 2015-07-22 20:01:14
○ 2015-11-18 10:56:48
○ 2026-06-24 06:38:48

○NSns-de.1and1-dns.org2015-07-22 → 2015-07-22 · 3 obs

● 2015-07-22 20:01:14
○ 2015-11-18 10:56:48
○ 2026-06-24 06:38:48

●NSns1.linode.com2026-03-23 → 2026-06-24 · 3 obs

○ 2020-02-03 00:53:02
● 2026-03-23 09:16:30
● 2026-06-24 06:38:48

○NSns17.domaincontrol.com2017-02-10 → 2017-02-10 · 4 obs

○ 2016-06-19 21:30:56
● 2017-02-10 07:55:48
○ 2020-02-03 00:53:02
○ 2026-06-24 06:38:48

○NSns18.domaincontrol.com2017-02-10 → 2017-02-10 · 4 obs

○ 2016-06-19 21:30:56
● 2017-02-10 07:55:48
○ 2020-02-03 00:53:02
○ 2026-06-24 06:38:48

●NSns2.linode.com2026-03-23 → 2026-06-24 · 3 obs

○ 2020-02-03 00:53:02
● 2026-03-23 09:16:30
● 2026-06-24 06:38:48

●NSns3.linode.com2026-03-23 → 2026-06-24 · 3 obs

○ 2020-02-03 00:53:02
● 2026-03-23 09:16:30
● 2026-06-24 06:38:48

●NSns4.linode.com2026-03-23 → 2026-06-24 · 3 obs

○ 2020-02-03 00:53:02
● 2026-03-23 09:16:30
● 2026-06-24 06:38:48

●NSns5.linode.com2026-03-23 → 2026-06-24 · 3 obs

○ 2020-02-03 00:53:02
● 2026-03-23 09:16:30
● 2026-06-24 06:38:48

○MXmailgw.ns36.de2015-11-18 → 2016-02-27 · 5 obs

○ 2015-07-22 20:01:14
● 2015-11-18 10:56:48
● 2016-02-27 17:40:28
○ 2016-06-19 21:30:56
○ 2026-06-24 06:38:48

○MXmailstore1.secureserver.net2017-02-10 → 2017-02-10 · 4 obs

○ 2016-06-19 21:30:56
● 2017-02-10 07:55:48
○ 2020-02-03 00:53:02
○ 2026-06-24 06:38:48

●MXmx.yandex.net2026-03-23 → 2026-06-24 · 3 obs

○ 2020-02-03 00:53:02
● 2026-03-23 09:16:30
● 2026-06-24 06:38:48

○MXmx00.kundenserver.de2015-07-22 → 2015-07-22 · 3 obs

● 2015-07-22 20:01:14
○ 2015-11-18 10:56:48
○ 2026-06-24 06:38:48

○MXmx01.kundenserver.de2015-07-22 → 2015-07-22 · 3 obs

● 2015-07-22 20:01:14
○ 2015-11-18 10:56:48
○ 2026-06-24 06:38:48

○MXsmtp.secureserver.net2017-02-10 → 2017-02-10 · 4 obs

○ 2016-06-19 21:30:56
● 2017-02-10 07:55:48
○ 2020-02-03 00:53:02
○ 2026-06-24 06:38:48

○A184.168.221.452017-02-10 → 2017-02-10 · 4 obs

○ 2016-06-19 21:30:56
● 2017-02-10 07:55:48
○ 2020-02-03 00:53:02
○ 2026-06-24 06:38:48

○A217.160.178.1652015-07-22 → 2015-07-22 · 3 obs

● 2015-07-22 20:01:14
○ 2015-11-18 10:56:48
○ 2026-06-24 06:38:48

○A72.52.4.902015-11-18 → 2016-02-27 · 5 obs

○ 2015-07-22 20:01:14
● 2015-11-18 10:56:48
● 2016-02-27 17:40:28
○ 2016-06-19 21:30:56
○ 2026-06-24 06:38:48

●A89.108.75.662026-03-23 → 2026-06-24 · 3 obs

○ 2020-02-03 00:53:02
● 2026-03-23 09:16:30
● 2026-06-24 06:38:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
connect-api.com	ns1.linode.com, ns2.linode.com, ns3.linode.com	6 records

✅ Authoritative Response

Server:92.123.94.2

NS records: ns1.linode.com, ns2.linode.com, ns3.linode.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for connect-api.com (unsigned zone)

⏱️ Timing

Total: 338ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`89.108.75.66`
NS	5	`ns4.linode.com, ns2.linode.com...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 redirect=_spf.yandex.net`
SOA	1	`ns1.linode.com info.connect-api.com`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.linode.com, ns1.linode.com, ns2.linode.com...)

Analysis

IP Addresses

connect-api.com directs to one IP number, which is 89.108.75.66.

Name Servers

The authoritative name servers for connect-api.com are ns1.linode.com, ns2.linode.com, ns3.linode.com and two others.

There is at least partial name server overlap between connect-api.com and other domains — astllc.org, robby.ca, writinghelpdesk.com and two more among them.

These name servers frequently co-occur with the name servers ns4.linode.com and ns5.linode.com.

Hosts with two IP numbers each:

ns1.linode.com has two IP addresses: 92.123.94.2 and 2600:14c0:6::2.

ns2.linode.com has two IP addresses: 92.123.94.3 and 2600:14c0:6::3.

ns3.linode.com has two IP addresses: 92.123.95.3 and 2600:14c0:7::3.

ns4.linode.com has two IP addresses: 92.123.95.4 and 2600:14c0:7::4.

ns5.linode.com has two IP addresses: 92.123.95.2 and 2600:14c0:7::2.

Mail Servers

connect-api.com routes its mail through a single mail server, mx.yandex.net.

connect-api.com has the same mail server arrangement as a number of other domains, for example unga.ru, 1a9.ru, alva-donna.ru and two more.

mx.yandex.net carries two IP numbers: 77.88.21.249 and 2a02:6b8::311.