securegateways.com - dns.ninja

`securegateways.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:24d6^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3030::ac43:c7c1^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.36.214^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.199.193^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ns1.domainmanage.com` ⭐
		A	2400:cb00:2049:1::adf5:3b04^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	173.245.59.4^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.domainmanage.com`
		A	2400:cb00:2049:1::c629:df27^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	198.41.223.39^{Cloudflare198.41.223.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`cf-198-41-223-39.cloudflare.com`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.36.214, 172.67.199.193
		IPv6 hints	2606:4700:3030::6815:24d6, 2606:4700:3030::ac43:c7c1
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=218, name=cloudflare-ech.com
SOA	`ns1.domainmanage.com`dns@cloudflare.com serial=2408095644

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

Same first word

securegateways.com

DNS History

16 records (6 active, 10 former)

○NSbuy.internettraffic.com2015-07-09 → 2016-05-02 · 4 obs

● 2015-07-09 19:37:28
● 2016-05-02 17:13:14
○ 2017-02-04 20:56:04
○ 2026-08-01 21:55:06

○NSns1.afternic.com2026-05-18 → 2026-05-18 · 3 obs

○ 2017-02-04 20:56:04
● 2026-05-18 02:26:12
○ 2026-08-01 21:55:06

●NSns1.domainmanage.com2026-08-01 → 2026-08-01 · 2 obs

○ 2026-05-18 02:26:12
● 2026-08-01 21:55:06

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

○ 2016-05-02 17:13:14
● 2017-02-04 20:56:04
○ 2026-05-18 02:26:12
○ 2026-08-01 21:55:06

○NSns2.afternic.com2026-05-18 → 2026-05-18 · 3 obs

○ 2017-02-04 20:56:04
● 2026-05-18 02:26:12
○ 2026-08-01 21:55:06

●NSns2.domainmanage.com2026-08-01 → 2026-08-01 · 2 obs

○ 2026-05-18 02:26:12
● 2026-08-01 21:55:06

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

○ 2016-05-02 17:13:14
● 2017-02-04 20:56:04
○ 2026-05-18 02:26:12
○ 2026-08-01 21:55:06

○NSsell.internettraffic.com2015-07-09 → 2016-05-02 · 4 obs

● 2015-07-09 19:37:28
● 2016-05-02 17:13:14
○ 2017-02-04 20:56:04
○ 2026-08-01 21:55:06

●A104.21.36.2142026-08-01 → 2026-08-01 · 2 obs

○ 2026-05-18 02:26:12
● 2026-08-01 21:55:06

○A13.248.169.482026-05-18 → 2026-05-18 · 3 obs

○ 2017-02-04 20:56:04
● 2026-05-18 02:26:12
○ 2026-08-01 21:55:06

●A172.67.199.1932026-08-01 → 2026-08-01 · 2 obs

○ 2026-05-18 02:26:12
● 2026-08-01 21:55:06

●A2606:4700:3030::6815:24d62026-08-01 → 2026-08-01 · 2 obs

○ 2026-05-18 02:26:12
● 2026-08-01 21:55:06

●A2606:4700:3030::ac43:c7c12026-08-01 → 2026-08-01 · 2 obs

○ 2026-05-18 02:26:12
● 2026-08-01 21:55:06

○A69.172.201.1532016-05-02 → 2017-02-04 · 5 obs

○ 2016-02-12 15:01:36
● 2016-05-02 17:13:14
● 2017-02-04 20:56:04
○ 2026-05-18 02:26:12
○ 2026-08-01 21:55:06

○A69.172.201.2082015-07-09 → 2016-02-12 · 4 obs

● 2015-07-09 19:37:28
● 2016-02-12 15:01:36
○ 2016-05-02 17:13:14
○ 2026-08-01 21:55:06

○A76.223.54.1462026-05-18 → 2026-05-18 · 3 obs

○ 2017-02-04 20:56:04
● 2026-05-18 02:26:12
○ 2026-08-01 21:55:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
securegateways.com	ns1.domainmanage.com, ns2.domainmanage.com	2 records

✅ Authoritative Response

Server:198.41.223.39

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securegateways.com (unsigned zone)

⏱️ Timing

Total: 180ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.36.214, 172.67.199.193`
AAAA	2	`2606:4700:3030::6815:24d6, 2606:4700:3030::ac43:c7c1`
NS	2	`ns1.domainmanage.com, ns2.domainmanage.com`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ns1.domainmanage.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

securegateways.com has four IP addresses: 104.21.36.214, 172.67.199.193, 2606:4700:3030::6815:24d6 and 2606:4700:3030::ac43:c7c1.

codeigniter.org, coin-bonus.org, propertylink.co.zw and two other host names share IP numbers with securegateways.com.

Name Servers

Two name servers handle the delegation for securegateways.com: ns1.domainmanage.com and ns2.domainmanage.com.

securegateways.com uses the same name servers as several other domains — among them diffracto.com, medi-clinic.com, searchportland.com and two more.

ns1.domainmanage.com and ns2.domainmanage.com both carry two IP addresses. The A records for ns1.domainmanage.com are 173.245.59.4 and 2400:cb00:2049:1::adf5:3b04; the A records for ns2.domainmanage.com are 198.41.223.39 and 2400:cb00:2049:1::c629:df27.