buildnotify.dev - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`buildnotify.dev`

DNSSEC	⚠️ Not signed
NS	`elias.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c1d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elias.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c31d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`elias.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:231d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`elias.ns.cloudflare.com`
		A	108.162.195.29^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elias.ns.cloudflare.com`
		A	162.159.44.29^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elias.ns.cloudflare.com`
		A	172.64.35.29^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elias.ns.cloudflare.com`
NS	`paislee.ns.cloudflare.com`
		A	2606:4700:50::a29f:26b7^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paislee.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2b7^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`paislee.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22b7^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`paislee.ns.cloudflare.com`
		A	108.162.194.183^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paislee.ns.cloudflare.com`
		A	162.159.38.183^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paislee.ns.cloudflare.com`
		A	172.64.34.183^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paislee.ns.cloudflare.com`
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}
			PTR	`route1.mx.cloudflare.net`
		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}
			PTR	`route1.mx.cloudflare.net`
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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`elias.ns.cloudflare.com`dns@cloudflare.com serial=2416236605

`dev`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=1

🔒 HSTS Preload (+subdomains)

Same first word

buildnotify.dev

Similar names

notifybuild.net

notifybuild.com

Previous names

Next names

DNS History

5 records (5 active, 0 former)

●NSelias.ns.cloudflare.com2026-09-11 → 2026-11-02 · 2 obs

● 2026-09-11 21:48:20
● 2026-11-02 18:51:58

●NSpaislee.ns.cloudflare.com2026-09-11 → 2026-11-02 · 2 obs

● 2026-09-11 21:48:20
● 2026-11-02 18:51:58

●MXroute1.mx.cloudflare.net2026-09-11 → 2026-11-02 · 2 obs

● 2026-09-11 21:48:20
● 2026-11-02 18:51:58

●MXroute2.mx.cloudflare.net2026-09-11 → 2026-11-02 · 2 obs

● 2026-09-11 21:48:20
● 2026-11-02 18:51:58

●MXroute3.mx.cloudflare.net2026-09-11 → 2026-11-02 · 2 obs

● 2026-09-11 21:48:20
● 2026-11-02 18:51:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
buildnotify.dev	paislee.ns.cloudflare.com, elias.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.34.183

NS records: paislee.ns.cloudflare.com, elias.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for buildnotify.dev (unsigned zone)

⏱️ Timing

Total: 1401ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`elias.ns.cloudflare.com, paislee.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 18), route3.mx.cloudflare.net (pri: 25)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`elias.ns.cloudflare.com dns.cloudflare.c`

Analysis

Name Servers

Two name servers handle the delegation for buildnotify.dev: elias.ns.cloudflare.com and paislee.ns.cloudflare.com.

buildnotify.dev shares its name server setup with other domains, including zy-cc.workers.dev, shopmbclub.com, eaccountableleadgeneration.info and two others.

There is at least partial name server overlap between buildnotify.dev and other domains — hsck02.cc, surgerysite.co.uk, xxvmpef.shop and two more among them.

These name servers are frequently paired with the name servers priscilla.ns.cloudflare.com, ace.ns.cloudflare.com, gigi.ns.cloudflare.com and two others.

Host names with 6 IP numbers:

elias.ns.cloudflare.com resolves to 108.162.195.29, 162.159.44.29 and 172.64.35.29 among others, with 3 other IP addresses in total.

paislee.ns.cloudflare.com resolves to 108.162.194.183, 162.159.38.183 and 172.64.34.183 among others, with 3 other IP addresses in total.

Mail Servers

Incoming mail for buildnotify.dev is delivered via three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

buildnotify.dev shares mail servers — at least in part — with other domains, including threepawspets.com, engiemiddleeast.net, dlocs.com and two others.

Host names with 6 IP numbers:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.