secureverified.com - dns.ninja

`secureverified.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::6815:68b^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3035::ac43:9ae4^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.6.139^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.154.228^{🇺🇸 Cloudflare172.67.144.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.6.139, 172.67.154.228
		IPv6 hints	2606:4700:3035::6815:68b, 2606:4700:3035::ac43:9ae4
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=94, name=cloudflare-ech.com
SOA	`ns1.domainmanage.com`dns@cloudflare.com serial=2408095693

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

Same first word

secureverified.com

Similar names

verifiedsecure.org

verifiedsecure.com

verifiedrescue.net

DNS History

16 records (6 active, 10 former)

○NSbuy.internettraffic.com2015-08-03 → 2016-07-13 · 4 obs

● 2015-08-03 15:50:54
● 2016-07-13 06:22:42
○ 2017-05-16 14:00:26
○ 2026-08-05 15:14:24

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

○ 2017-05-16 14:00:26
● 2026-05-18 15:53:06
○ 2026-08-05 15:14:24

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

○ 2026-05-18 15:53:06
● 2026-08-05 15:14:24

○NSns1.uniregistrymarket.link2017-05-16 → 2017-05-16 · 4 obs

○ 2016-07-13 06:22:42
● 2017-05-16 14:00:26
○ 2026-05-18 15:53:06
○ 2026-08-05 15:14:24

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

○ 2017-05-16 14:00:26
● 2026-05-18 15:53:06
○ 2026-08-05 15:14:24

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

○ 2026-05-18 15:53:06
● 2026-08-05 15:14:24

○NSns2.uniregistrymarket.link2017-05-16 → 2017-05-16 · 4 obs

○ 2016-07-13 06:22:42
● 2017-05-16 14:00:26
○ 2026-05-18 15:53:06
○ 2026-08-05 15:14:24

○NSsell.internettraffic.com2015-08-03 → 2016-07-13 · 4 obs

● 2015-08-03 15:50:54
● 2016-07-13 06:22:42
○ 2017-05-16 14:00:26
○ 2026-08-05 15:14:24

●A104.21.6.1392026-08-05 → 2026-08-05 · 2 obs

○ 2026-05-18 15:53:06
● 2026-08-05 15:14:24

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

○ 2017-05-16 14:00:26
● 2026-05-18 15:53:06
○ 2026-08-05 15:14:24

●A172.67.154.2282026-08-05 → 2026-08-05 · 2 obs

○ 2026-05-18 15:53:06
● 2026-08-05 15:14:24

●A2606:4700:3035::6815:68b2026-08-05 → 2026-08-05 · 2 obs

○ 2026-05-18 15:53:06
● 2026-08-05 15:14:24

●A2606:4700:3035::ac43:9ae42026-08-05 → 2026-08-05 · 2 obs

○ 2026-05-18 15:53:06
● 2026-08-05 15:14:24

○A69.172.201.1532016-07-13 → 2017-05-16 · 5 obs

○ 2016-03-11 17:42:16
● 2016-07-13 06:22:42
● 2017-05-16 14:00:26
○ 2026-05-18 15:53:06
○ 2026-08-05 15:14:24

○A69.172.201.2082015-08-03 → 2016-03-11 · 4 obs

● 2015-08-03 15:50:54
● 2016-03-11 17:42:16
○ 2016-07-13 06:22:42
○ 2026-08-05 15:14:24

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

○ 2017-05-16 14:00:26
● 2026-05-18 15:53:06
○ 2026-08-05 15:14:24

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:173.245.59.4

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for secureverified.com (unsigned zone)

⏱️ Timing

Total: 108ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.6.139, 172.67.154.228`
AAAA	2	`2606:4700:3035::ac43:9ae4, 2606:4700:3035::6815:68b`
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

secureverified.com has four IP addresses: 104.21.6.139, 172.67.154.228, 2606:4700:3035::6815:68b and 2606:4700:3035::ac43:9ae4.

duga.thub.lol, www.brickts.com, anysolver.io and two other host names share IP numbers with secureverified.com.

Name Servers

secureverified.com is served by two delegated name servers, ns1.domainmanage.com and ns2.domainmanage.com.

secureverified.com uses the same name servers as several other domains — among them ski-zone.com, lamusicaclasica.com, u-i.net and two more.

The DNS delegation for secureverified.com at least partly coincides with that of other domains, domainmanage.com being one example.

Each of the two host names carries two IP addresses: ns1.domainmanage.com points to 173.245.59.4 and 2400:cb00:2049:1::adf5:3b04, and ns2.domainmanage.com points to 198.41.223.39 and 2400:cb00:2049:1::c629:df27.