projectdatabase.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`projectdatabase.com`

DNSSEC	⚠️ Not signed
A	92.205.15.114^{🇫🇷 GODADDY-SXB92.205.0.0/20}
		PTR	`114.15.205.92.host.secureserver.net`
NS	`ns19.domaincontrol.com` ⭐
		A	2603:5:21d0::a^{🇺🇸 GODADDY-DNS2603:5:21d0::/44}
			PTR	`ns19.domaincontrol.com`
		A	97.74.109.10^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns19.domaincontrol.com`
NS	`ns20.domaincontrol.com`
		A	2603:5:22d0::a^{🇺🇸 GODADDY-DNS2603:5:22d0::/44}
			PTR	`ns20.domaincontrol.com`
		A	173.201.77.10^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns20.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	142.251.111.26^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
SOA	`ns19.domaincontrol.com`dns@jomax.net 2024-03-06 #0

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

Subdomains

fw.projectdatabase.com

server1.projectdatabase.com

Same first word

projectdatabase.com

Previous names

Next names

DNS History

12 records (8 active, 4 former)

○NSns.123-reg.co.uk2015-08-05 → 2018-05-27 · 5 obs

○ 2009-01-11 19:25:18
● 2015-08-05 08:42:56
● 2018-05-27 04:10:22
○ 2026-03-19 16:20:00
○ 2026-08-18 08:20:04

●NSns19.domaincontrol.com2026-03-19 → 2026-08-18 · 3 obs

○ 2018-05-27 04:10:22
● 2026-03-19 16:20:00
● 2026-08-18 08:20:04

○NSns2.123-reg.co.uk2015-08-05 → 2018-05-27 · 5 obs

○ 2009-01-11 19:25:18
● 2015-08-05 08:42:56
● 2018-05-27 04:10:22
○ 2026-03-19 16:20:00
○ 2026-08-18 08:20:04

●NSns20.domaincontrol.com2026-03-19 → 2026-08-18 · 3 obs

○ 2018-05-27 04:10:22
● 2026-03-19 16:20:00
● 2026-08-18 08:20:04

●MXalt1.aspmx.l.google.com2015-08-05 → 2026-08-18 · 3 obs

○ 2009-01-11 19:25:18
● 2015-08-05 08:42:56
● 2026-08-18 08:20:04

●MXalt2.aspmx.l.google.com2015-08-05 → 2026-08-18 · 3 obs

○ 2009-01-11 19:25:18
● 2015-08-05 08:42:56
● 2026-08-18 08:20:04

●MXaspmx.l.google.com2015-08-05 → 2026-08-18 · 3 obs

○ 2009-01-11 19:25:18
● 2015-08-05 08:42:56
● 2026-08-18 08:20:04

●MXaspmx2.googlemail.com2015-08-05 → 2026-08-18 · 3 obs

○ 2009-01-11 19:25:18
● 2015-08-05 08:42:56
● 2026-08-18 08:20:04

●MXaspmx3.googlemail.com2015-08-05 → 2026-08-18 · 3 obs

○ 2009-01-11 19:25:18
● 2015-08-05 08:42:56
● 2026-08-18 08:20:04

○A194.154.164.1002009-01-11 → 2009-01-11 · 3 obs

● 2009-01-11 19:25:18
○ 2015-08-05 08:42:56
○ 2026-08-18 08:20:04

●A92.205.15.1142026-03-19 → 2026-08-18 · 3 obs

○ 2018-05-27 04:10:22
● 2026-03-19 16:20:00
● 2026-08-18 08:20:04

○A94.136.40.1032015-08-05 → 2018-05-27 · 5 obs

○ 2009-01-11 19:25:18
● 2015-08-05 08:42:56
● 2018-05-27 04:10:22
○ 2026-03-19 16:20:00
○ 2026-08-18 08:20:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net, g.gtld-servers.net...	-
projectdatabase.com	ns19.domaincontrol.com, ns20.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.109.10

NS records: ns19.domaincontrol.com, ns20.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for projectdatabase.com (unsigned zone)

⏱️ Timing

Total: 857ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`92.205.15.114`
NS	2	`ns19.domaincontrol.com, ns20.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)...`
SOA	1	`ns19.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns19.domaincontrol.com, ns19.domaincontrol.com, ns20.domaincontrol.com...)

Analysis

Hierarchy

fw.projectdatabase.com and server1.projectdatabase.com each fall under projectdatabase.com as their parent domain.

IP Addresses

projectdatabase.com resolves to just one IP address, 92.205.15.114.

Two other host names, along with asemcol.com, takemyparcel.com and www.single-photon.com, also share IP numbers with projectdatabase.com.

Name Servers

projectdatabase.com uses two name servers for its delegation: ns19.domaincontrol.com and ns20.domaincontrol.com.

projectdatabase.com shares its NS records with other domains, for example hibberthomes.co.uk, bsbmemo.com, buildingdigitalmind.com and two others.

The two host names ns19.domaincontrol.com and ns20.domaincontrol.com each have a pair of IP addresses: ns19.domaincontrol.com has 97.74.109.10 and 2603:5:21d0::a, and ns20.domaincontrol.com has 173.201.77.10 and 2603:5:22d0::a.

Mail Servers

projectdatabase.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between projectdatabase.com and other domains, including agentsdata.com.au, tcl.coffee, shopmobility.org.je and two others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com directs traffic to 142.251.111.26 and 2607:f8b0:4004:c1d::1a.

alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1a IP addresses each.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 192.178.234.27 IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.