managedlogistics.com - dns.ninja

`managedlogistics.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns2.afternic.com` ⭐
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`ns1.afternic.com`
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
TXT	`v=spf1 -all`
SOA	`ns2.afternic.com`dns@jomax.net serial=1

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

Same first word

managedlogistics.com

DNS History

21 records (4 active, 17 former)

○NSdns1.name-services.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○NSdns2.name-services.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○NSdns3.name-services.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○NSdns4.name-services.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○NSdns5.name-services.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

●NSns1.afternic.com2026-04-02 → 2026-07-31 · 3 obs

○ 2017-04-19 10:13:24
● 2026-04-02 22:27:12
● 2026-07-31 11:11:18

○NSns1.uniregistrymarket.link2017-04-19 → 2017-04-19 · 4 obs

○ 2016-09-18 12:42:10
● 2017-04-19 10:13:24
○ 2026-04-02 22:27:12
○ 2026-07-31 11:11:18

●NSns2.afternic.com2026-04-02 → 2026-07-31 · 3 obs

○ 2017-04-19 10:13:24
● 2026-04-02 22:27:12
● 2026-07-31 11:11:18

○NSns2.uniregistrymarket.link2017-04-19 → 2017-04-19 · 4 obs

○ 2016-09-18 12:42:10
● 2017-04-19 10:13:24
○ 2026-04-02 22:27:12
○ 2026-07-31 11:11:18

○MXalt1.aspmx.l.google.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○MXalt2.aspmx.l.google.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○MXaspmx.l.google.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○MXaspmx2.googlemail.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○MXaspmx3.googlemail.com2015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

●A13.248.169.482026-04-02 → 2026-07-31 · 3 obs

○ 2017-04-19 10:13:24
● 2026-04-02 22:27:12
● 2026-07-31 11:11:18

○A216.239.32.212015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○A216.239.34.212015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○A216.239.36.212015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○A216.239.38.212015-05-20 → 2016-09-18 · 4 obs

● 2015-05-20 05:32:00
● 2016-09-18 12:42:10
○ 2017-04-19 10:13:24
○ 2026-07-31 11:11:18

○A69.172.201.1532017-04-19 → 2017-04-19 · 4 obs

○ 2016-09-18 12:42:10
● 2017-04-19 10:13:24
○ 2026-04-02 22:27:12
○ 2026-07-31 11:11:18

●A76.223.54.1462026-04-02 → 2026-07-31 · 3 obs

○ 2017-04-19 10:13:24
● 2026-04-02 22:27:12
● 2026-07-31 11:11:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, f.gtld-servers.net, h.gtld-servers.net, l.gtld-servers.net...	-
managedlogistics.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:173.201.66.69

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for managedlogistics.com (unsigned zone)

⏱️ Timing

Total: 242ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns2.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

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

Analysis

IP Addresses

managedlogistics.com has two IP addresses: 13.248.169.48 and 76.223.54.146

Among the host names that share IP numbers with managedlogistics.com are corkbark.com, hostmaster.keepballin.com, unscene.org and two others.

Name Servers

managedlogistics.com uses two name servers for its delegation: ns1.afternic.com and ns2.afternic.com.

managedlogistics.com has the same name server delegation as a number of other domains, such as 1portfolio.com, megahertz.net, totsuki.com and two more.

The name servers of managedlogistics.com overlap at least partially with those of other domains — among them webaraci.com, elitex.online, engageo.com and two more.

These name servers commonly appear alongside the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

The two host names ns1.afternic.com and ns2.afternic.com each have a pair of IP addresses: ns1.afternic.com has 97.74.98.69 and 2603:5:2126::45, and ns2.afternic.com has 173.201.66.69 and 2603:5:2226::45.