projectalert.com - dns.ninja
projectalert.com
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.netnstld@verisign-grs.com serial=1786574394 | ||||||
Same first word
projectalert.org |
projectalert.com |
Similar names
DNS History
23 records (8 active, 15 former)
○NSauthns1.centurylink.net2017-07-17 → 2017-09-12 · 5 obs
● 2017-07-17 00:19:52
● 2017-09-12 17:29:56
○ 2026-05-11 03:15:14
○ 2026-08-12 23:03:24
○NSauthns2.centurylink.net2017-07-17 → 2017-09-12 · 5 obs
● 2017-07-17 00:19:52
● 2017-09-12 17:29:56
○ 2026-05-11 03:15:14
○ 2026-08-12 23:03:24
○NSdns1.rand.org2015-07-04 → 2017-09-12 · 4 obs
● 2017-09-12 17:29:56
○ 2026-05-11 03:15:14
○ 2026-08-12 23:03:24
○NSdns2.rand.org2015-07-04 → 2017-09-12 · 4 obs
● 2017-09-12 17:29:56
○ 2026-05-11 03:15:14
○ 2026-08-12 23:03:24
○NSdns3.rand.org2015-07-04 → 2017-09-12 · 4 obs
● 2017-09-12 17:29:56
○ 2026-05-11 03:15:14
○ 2026-08-12 23:03:24
●NSns-1098.awsdns-09.org2026-05-11 → 2026-08-12 · 3 obs
● 2026-05-11 03:15:14
● 2026-08-12 23:03:24
●NSns-1710.awsdns-21.co.uk2026-05-11 → 2026-08-12 · 3 obs
● 2026-05-11 03:15:14
● 2026-08-12 23:03:24
●NSns-588.awsdns-09.net2026-05-11 → 2026-08-12 · 3 obs
● 2026-05-11 03:15:14
● 2026-08-12 23:03:24
●NSns-71.awsdns-08.com2026-05-11 → 2026-08-12 · 3 obs
● 2026-05-11 03:15:14
● 2026-08-12 23:03:24
●MXinbound-smtp.us-west-2.amazonaws.com2026-05-11 → 2026-08-12 · 3 obs
● 2026-05-11 03:15:14
● 2026-08-12 23:03:24
○MXmail-ext.rand.org2015-07-04 → 2016-06-08 · 4 obs
● 2016-06-08 06:19:18
○ 2016-06-22 11:24:20
○ 2026-08-12 23:03:24
○A100.20.161.2442026-05-11 → 2026-05-11 · 3 obs
○ 2026-05-20 00:09:56
○ 2026-08-12 23:03:24
○A100.22.212.332026-05-20 → 2026-05-20 · 3 obs
● 2026-05-20 00:09:56
○ 2026-08-12 23:03:24
●A32.186.202.1662026-08-12 → 2026-08-12 · 2 obs
● 2026-08-12 23:03:24
○A34.216.145.1552026-05-11 → 2026-08-12 · 2 obs
○ 2026-08-12 23:03:24
○A35.160.230.1482026-05-20 → 2026-05-20 · 3 obs
● 2026-05-20 00:09:56
○ 2026-08-12 23:03:24
○A35.165.91.2412026-05-11 → 2026-05-11 · 3 obs
○ 2026-05-20 00:09:56
○ 2026-08-12 23:03:24
○A35.80.252.2372026-05-11 → 2026-08-12 · 2 obs
○ 2026-08-12 23:03:24
○A35.85.5.1972026-05-20 → 2026-05-20 · 3 obs
● 2026-05-20 00:09:56
○ 2026-08-12 23:03:24
●A44.241.139.1022026-08-12 → 2026-08-12 · 2 obs
● 2026-08-12 23:03:24
●A44.241.225.2242026-08-12 → 2026-08-12 · 2 obs
● 2026-08-12 23:03:24
○A54.213.138.1362026-05-11 → 2026-05-11 · 3 obs
○ 2026-05-20 00:09:56
○ 2026-08-12 23:03:24
○A54.71.146.2422026-05-11 → 2026-08-12 · 2 obs
○ 2026-08-12 23:03:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net... | - |
| projectalert.com | ns-71.awsdns-08.com, ns-588.awsdns-09.net, ns-1710.awsdns-21.co.uk, ns-1098.awsdns-09.org | 2 records |
✅ Authoritative Response
Server:205.251.194.76
NS records: ns-71.awsdns-08.com, ns-588.awsdns-09.net, ns-1710.awsdns-21.co.uk, ns-1098.awsdns-09.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for projectalert.com (unsigned zone)
⏱️ Timing
Total: 447ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 3 | 32.186.202.166, 44.241.225.224... |
| NS | 4 | ns-1098.awsdns-09.org, ns-1710.awsdns-21.co.uk... |
| MX | 1 | inbound-smtp.us-west-2.amazonaws.com (pr |
| SOA | 1 | ns-71.awsdns-08.com awsdns-hostmaster.am |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-71.awsdns-08.com, ns-71.awsdns-08.com)
Analysis
IP Addresses
projectalert.com maps to three IP numbers — 32.186.202.166, 44.241.139.102 and 44.241.225.224.
Name Servers
The domain projectalert.com is delegated to these four name servers: ns-71.awsdns-08.com, ns-588.awsdns-09.net, ns-1098.awsdns-09.org and ns-1710.awsdns-21.co.uk.
projectalert.com has at least partial name server overlap with other domains, such as playcharmking.com, gaina-live.jp, lumeon.systems and two others.
ns-71.awsdns-08.com, ns-588.awsdns-09.net, ns-1098.awsdns-09.org and ns-1710.awsdns-21.co.uk all point to exactly two IP numbers each: ns-71.awsdns-08.com → 205.251.192.71 and 2600:9000:5300:4700::1; ns-588.awsdns-09.net → 205.251.194.76 and 2600:9000:5302:4c00::1; ns-1098.awsdns-09.org → 205.251.196.74 and 2600:9000:5304:4a00::1; ns-1710.awsdns-21.co.uk → 205.251.198.174 and 2600:9000:5306:ae00::1.
Mail Servers
projectalert.com routes its mail through a single mail server, inbound-smtp.us-west-2.amazonaws.com.
projectalert.com has the same mail server arrangement as a number of other domains, for example itsuki.tv, prod.fsniwaikato.kiwi, withcosme.com and two more.
projectalert.com shares at least some of its mail servers with other domains — for example stone.atlassian.net, vaxcare.atlassian.net, onecareconnection.atlassian.net and two more.
It is common for these mail servers to co-occur with inbound-smtp.us-east-1.amazonaws.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com as mail servers.
The host inbound-smtp.us-west-2.amazonaws.com directs to four IP numbers: 35.161.157.106, 52.13.163.116, 52.43.162.244 and 54.188.121.70.