🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`developmentleverage.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::ac43:db97^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::6815:18a0^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.24.160^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.219.151^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`austin.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b46^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`austin.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c146^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`austin.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2146^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`austin.ns.cloudflare.com`
		A	108.162.193.70^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`austin.ns.cloudflare.com`
		A	172.64.33.70^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`austin.ns.cloudflare.com`
		A	173.245.59.70^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`austin.ns.cloudflare.com`
NS	`maeve.ns.cloudflare.com`
		A	2606:4700:50::a29f:262d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`maeve.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c22d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`maeve.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:222d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`maeve.ns.cloudflare.com`
		A	108.162.194.45^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`maeve.ns.cloudflare.com`
		A	162.159.38.45^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`maeve.ns.cloudflare.com`
		A	172.64.34.45^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`maeve.ns.cloudflare.com`
MX	`route3.mx.cloudflare.net` ⭐
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁷²⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽⁷⁶⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.24.160, 172.67.219.151
		IPv6 hints	2606:4700:3030::ac43:db97, 2606:4700:3037::6815:18a0
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=201, name=cloudflare-ech.com
SOA	`austin.ns.cloudflare.com`dns@cloudflare.com serial=2415207552

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

Same first word

developmentleverage.com

Similar names

leveragedevelopment.com

Previous names

Next names

DNS History

21 records (9 active, 12 former)

●NSaustin.ns.cloudflare.com2026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

●NSmaeve.ns.cloudflare.com2026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

○NSns1.digitalocean.com2015-06-05 → 2016-11-26 · 4 obs

● 2015-06-05 00:43:44
● 2016-11-26 10:24:26
○ 2017-05-15 21:04:16
○ 2026-10-09 10:46:08

○NSns1034.ui-dns.com2017-05-15 → 2017-05-15 · 4 obs

○ 2016-11-26 10:24:26
● 2017-05-15 21:04:16
○ 2026-09-18 13:13:02
○ 2026-10-09 10:46:08

○NSns1035.ui-dns.de2017-05-15 → 2017-05-15 · 4 obs

○ 2016-11-26 10:24:26
● 2017-05-15 21:04:16
○ 2026-09-18 13:13:02
○ 2026-10-09 10:46:08

○NSns1040.ui-dns.biz2017-05-15 → 2017-05-15 · 4 obs

○ 2016-11-26 10:24:26
● 2017-05-15 21:04:16
○ 2026-09-18 13:13:02
○ 2026-10-09 10:46:08

○NSns1110.ui-dns.org2017-05-15 → 2017-05-15 · 4 obs

○ 2016-11-26 10:24:26
● 2017-05-15 21:04:16
○ 2026-09-18 13:13:02
○ 2026-10-09 10:46:08

○NSns2.digitalocean.com2015-06-05 → 2016-11-26 · 4 obs

● 2015-06-05 00:43:44
● 2016-11-26 10:24:26
○ 2017-05-15 21:04:16
○ 2026-10-09 10:46:08

○NSns3.digitalocean.com2015-06-05 → 2016-11-26 · 4 obs

● 2015-06-05 00:43:44
● 2016-11-26 10:24:26
○ 2017-05-15 21:04:16
○ 2026-10-09 10:46:08

○MXmx00.1and1.com2017-05-15 → 2017-05-15 · 3 obs

● 2017-05-15 21:04:16
○ 2026-09-18 13:13:02
○ 2026-10-09 10:46:08

○MXmx01.1and1.com2017-05-15 → 2017-05-15 · 3 obs

● 2017-05-15 21:04:16
○ 2026-09-18 13:13:02
○ 2026-10-09 10:46:08

●MXroute1.mx.cloudflare.net2026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

●MXroute2.mx.cloudflare.net2026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

●MXroute3.mx.cloudflare.net2026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

●A104.21.24.1602026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

●A172.67.219.1512026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

○A192.241.231.942015-06-05 → 2016-11-26 · 4 obs

● 2015-06-05 00:43:44
● 2016-11-26 10:24:26
○ 2017-05-15 21:04:16
○ 2026-10-09 10:46:08

○A216.250.120.1722017-05-15 → 2017-05-15 · 4 obs

○ 2016-11-26 10:24:26
● 2017-05-15 21:04:16
○ 2026-09-18 13:13:02
○ 2026-10-09 10:46:08

●A2606:4700:3030::ac43:db972026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

●A2606:4700:3037::6815:18a02026-09-18 → 2026-10-09 · 3 obs

○ 2017-05-15 21:04:16
● 2026-09-18 13:13:02
● 2026-10-09 10:46:08

○A2607:f1c0:1000:3060:f42b:6cf6:cbc7:30432017-05-15 → 2017-05-15 · 4 obs

○ 2016-11-26 10:24:26
● 2017-05-15 21:04:16
○ 2026-09-18 13:13:02
○ 2026-10-09 10:46:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
developmentleverage.com	austin.ns.cloudflare.com, maeve.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.70

NS records: austin.ns.cloudflare.com, maeve.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for developmentleverage.com (unsigned zone)

⏱️ Timing

Total: 384ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.24.160, 172.67.219.151`
AAAA	2	`2606:4700:3030::ac43:db97, 2606:4700:3037::6815:18a0`
NS	2	`austin.ns.cloudflare.com, maeve.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 22), route2.mx.cloudflare.net (pri: 72)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`austin.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (austin.ns.cloudflare.com, austin.ns.cloudflare.com, austin.ns.cloudflare.com...)

Analysis

IP Addresses

developmentleverage.com has four IP addresses: 104.21.24.160, 172.67.219.151, 2606:4700:3030::ac43:db97 and 2606:4700:3037::6815:18a0.

pyramidglide.xyz, tiruchengodu.com, friends-status.com plus two other host names have IP numbers in common with developmentleverage.com.

Name Servers

developmentleverage.com uses two name servers for its delegation: austin.ns.cloudflare.com and maeve.ns.cloudflare.com.

The name server configuration of developmentleverage.com is shared with other domains, for instance m42nebula.com, asiga-pl.pages.dev, afl-player-movement-designs.pages.dev and two others.

developmentleverage.com partially shares its NS delegation with several other domains, including bobfarleymusic.com, yluhfegl.workers.dev, vombat.app and two others.

These name servers often co-occur with the name servers miki.ns.cloudflare.com.

Hosts with 6 IP addresses each:

Hostname austin.ns.cloudflare.com directs to 108.162.193.70, 172.64.33.70 and 173.245.59.70 along with 3 other IP addresses.

Hostname maeve.ns.cloudflare.com directs to 108.162.194.45, 162.159.38.45 and 172.64.34.45 along with 3 other IP addresses.

Mail Servers

developmentleverage.com uses three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

At least some of the mail servers used by developmentleverage.com are shared with other domains: radio.training, perchbird.app, kelvra.store and two others among them.

Hosts with 6 IP addresses each:

Hostname route1.mx.cloudflare.net directs to 162.159.205.11, 162.159.205.12 and 162.159.205.13 along with 3 other IP addresses.

Hostname route2.mx.cloudflare.net directs to 162.159.205.17, 162.159.205.18 and 162.159.205.19 along with 3 other IP addresses.

Hostname route3.mx.cloudflare.net directs to 162.159.205.23, 162.159.205.24 and 162.159.205.25 along with 3 other IP addresses.

developmentleverage.com - robtex.com