medintelnet.com - dns.ninja

`medintelnet.com`

DNSSEC	⚠️ Not signed
A	216.222.200.250
		PTR	`res-cp4.lax2.websiteservername.com`
NS	`ns1.websiteservername.com` ⭐ ⚠️ Not in parent delegation
		A	2400:cb00:2049:1::a29f:306a^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.48.106^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns1.fastsecureservers.com` ⚠️ Not in zone NS records
		A	162.159.48.106^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.fastsecureservers.com` ⚠️ Not in zone NS records
		A	162.159.49.242^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.websiteservername.com` ⚠️ Not in parent delegation
		A	2400:cb00:2049:1::a29f:31f2^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.49.242^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`medintelnet.com` ⭐
		A	216.222.200.250
			PTR	`res-cp4.lax2.websiteservername.com`
TXT	`v=spf1 ip4:216.222.200.250 ip4:204.44.192.77 +a +mx +include:spf.antispamclou...`
SOA	`ns1.websiteservername.com`admin@websiteservername.com 2026-06-24 #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=1782928761

MX for

medintelnet.com

Same first word

medintelnet.com

DNS History

17 records (6 active, 11 former)

○NSdns1.name-services.com2015-08-13 → 2016-03-22 · 4 obs

● 2015-08-13 17:42:04
● 2016-03-22 15:26:32
○ 2017-01-09 21:42:40
○ 2026-07-01 18:11:54

○NSdns2.name-services.com2015-08-13 → 2016-03-22 · 4 obs

● 2015-08-13 17:42:04
● 2016-03-22 15:26:32
○ 2017-01-09 21:42:40
○ 2026-07-01 18:11:54

○NSdns3.name-services.com2015-08-13 → 2016-03-22 · 4 obs

● 2015-08-13 17:42:04
● 2016-03-22 15:26:32
○ 2017-01-09 21:42:40
○ 2026-07-01 18:11:54

○NSdns4.name-services.com2015-08-13 → 2016-03-22 · 4 obs

● 2015-08-13 17:42:04
● 2016-03-22 15:26:32
○ 2017-01-09 21:42:40
○ 2026-07-01 18:11:54

○NSdns5.name-services.com2015-08-13 → 2016-03-22 · 4 obs

● 2015-08-13 17:42:04
● 2016-03-22 15:26:32
○ 2017-01-09 21:42:40
○ 2026-07-01 18:11:54

●NSns1.fastsecureservers.com2017-01-09 → 2026-07-01 · 3 obs

○ 2016-03-22 15:26:32
● 2017-01-09 21:42:40
● 2026-07-01 18:11:54

●NSns1.websiteservername.com2026-06-15 → 2026-07-01 · 3 obs

○ 2026-05-05 22:56:34
● 2026-06-15 01:07:28
● 2026-07-01 18:11:54

●NSns2.fastsecureservers.com2017-01-09 → 2026-07-01 · 3 obs

○ 2016-03-22 15:26:32
● 2017-01-09 21:42:40
● 2026-07-01 18:11:54

●NSns2.websiteservername.com2026-06-15 → 2026-07-01 · 3 obs

○ 2026-05-05 22:56:34
● 2026-06-15 01:07:28
● 2026-07-01 18:11:54

○NSns2011.websiteservername.com2026-05-05 → 2026-05-05 · 4 obs

○ 2017-01-09 21:42:40
● 2026-05-05 22:56:34
○ 2026-06-15 01:07:28
○ 2026-07-01 18:11:54

○NSns2012.websiteservername.com2026-05-05 → 2026-05-05 · 4 obs

○ 2017-01-09 21:42:40
● 2026-05-05 22:56:34
○ 2026-06-15 01:07:28
○ 2026-07-01 18:11:54

○MXmail.medintelnet.com2015-08-13 → 2016-03-22 · 4 obs

● 2015-08-13 17:42:04
● 2016-03-22 15:26:32
○ 2017-01-09 21:42:40
○ 2026-07-01 18:11:54

●MXmedintelnet.com2017-01-09 → 2026-07-01 · 3 obs

○ 2016-03-22 15:26:32
● 2017-01-09 21:42:40
● 2026-07-01 18:11:54

○A204.44.192.772026-05-05 → 2026-05-05 · 4 obs

○ 2018-01-09 14:11:04
● 2026-05-05 22:56:34
○ 2026-06-15 01:07:28
○ 2026-07-01 18:11:54

●A216.222.200.2502026-06-15 → 2026-07-01 · 3 obs

○ 2026-05-05 22:56:34
● 2026-06-15 01:07:28
● 2026-07-01 18:11:54

○A66.193.46.1812015-08-13 → 2016-03-22 · 4 obs

● 2015-08-13 17:42:04
● 2016-03-22 15:26:32
○ 2017-01-09 21:42:40
○ 2026-07-01 18:11:54

○A74.50.21.1372017-01-09 → 2018-01-09 · 5 obs

○ 2016-03-22 15:26:32
● 2017-01-09 21:42:40
● 2018-01-09 14:11:04
○ 2026-05-05 22:56:34
○ 2026-07-01 18:11:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net...	-
medintelnet.com	ns1.fastsecureservers.com, ns2.fastsecureservers.com	2 records

✅ Authoritative Response

Server:162.159.49.242

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for medintelnet.com (unsigned zone)

⏱️ Timing

Total: 2171ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.222.200.250`
NS	2	`ns1.websiteservername.com, ns2.websiteservername.com`
MX	1	`medintelnet.com (pri: 0)`
TXT	1	`v=spf1 ip4:216.222.200.250 ip4:204.44.19`
SOA	1	`ns1.websiteservername.com admin.websites`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.fastsecureservers.com, ns2.fastsecureservers.com)

Analysis

Mail Server Role

medintelnet.com handles its own mail, functioning as its own mail server.

IP Addresses

medintelnet.com resolves to just one IP address, 216.222.200.250.

Two other host names, along with stayinlakehavasu.com, lrgmouth.com and mail.zumeprint.com, also share IP numbers with medintelnet.com.

Name Servers

The NS records for medintelnet.com point to four name servers: ns1.fastsecureservers.com, ns2.fastsecureservers.com, ns1.websiteservername.com and ns2.websiteservername.com.

There is at least partial name server overlap between medintelnet.com and other domains — mcfan.info, laserinmotion.com, jfip.com and two more among them.

These name servers regularly appear alongside ns2021.websiteservername.com, ns2022.websiteservername.com, ns1301.websiteservername.com and 7 other name servers in NS record sets.

Host names that have two IP addresses:

The A records for ns1.websiteservername.com return 162.159.48.106 and 2400:cb00:2049:1::a29f:306a.

The A records for ns2.websiteservername.com return 162.159.49.242 and 2400:cb00:2049:1::a29f:31f2.

Host names that point to one IP address:

ns1.fastsecureservers.com resolves to the IP address 162.159.48.106.

ns2.fastsecureservers.com resolves to the IP address 162.159.49.242.

ns1.websiteservername.com and ns1.fastsecureservers.com each have 162.159.48.106 IP addresses.

ns2.websiteservername.com and ns2.fastsecureservers.com each have 162.159.49.242 IP addresses.

Mail Servers

medintelnet.com is served by just one mail server: medintelnet.com.

medintelnet.com resolves to 216.222.200.250 and no other IP number.