projectfedena.com - robtex.com
projectfedena.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.bluehost.com ⭐ ⚠️ Not in zone NS records | ||||||
| A | 162.159.24.80Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.bluehost.com | ||||||
| NS | ns-499.awsdns-62.com ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5301:f300::1🇺🇸 Amazon2600:9000:5301::/48 - CloudFront | ||||||
| PTR | ns-499.awsdns-62.com | ||||||
| A | 205.251.193.243🇺🇸 Amazon205.251.193.0/24 prefix | ||||||
| PTR | ns-499.awsdns-62.com | ||||||
| SOA | ns1.bluehost.comroot@box2425.bluehost.com 2022-10-05 #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.netnstld@verisign-grs.com serial=1771291435 | ||||||
Previously MX for
projectfedena.com |
Same first word
projectfedena.org |
projectfedena.com |
DNS History
6 records (2 active, 4 former)
●NSns-499.awsdns-62.com2026-02-17 → 2026-03-18 · 3 obs
● 2026-02-17 13:10:26
● 2026-03-18 09:02:56
●NSns1.bluehost.com2015-06-24 → 2026-03-18 · 2 obs
● 2026-03-18 09:02:56
○NSns2.bluehost.com2015-06-24 → 2026-03-12 · 9 obs
● 2017-06-17 02:09:52
○ 2026-02-17 13:10:26
● 2026-02-17 16:25:26
● 2026-02-17 17:54:40
○ 2026-02-21 23:23:52
● 2026-03-01 03:14:52
● 2026-03-12 06:57:12
○ 2026-03-18 09:02:56
○MXprojectfedena.com2015-06-24 → 2026-02-17 · 7 obs
● 2017-06-17 02:09:52
○ 2026-02-17 13:10:26
● 2026-02-17 16:25:26
● 2026-02-17 17:54:40
○ 2026-02-21 23:23:52
○ 2026-03-18 09:02:56
○A69.89.25.1582015-06-24 → 2017-06-17 · 4 obs
● 2017-06-17 02:09:52
○ 2026-02-17 13:10:26
○ 2026-03-18 09:02:56
○A74.220.219.1452026-02-17 → 2026-03-12 · 6 obs
● 2026-02-17 13:10:26
○ 2026-02-17 16:25:26
○ 2026-03-01 03:14:52
● 2026-03-12 06:57:12
○ 2026-03-18 09:02:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, c.gtld-servers.net, m.gtld-servers.net, k.gtld-servers.net... | - |
| projectfedena.com | ns1.bluehost.com, ns-499.awsdns-62.com | 2 records |
✅ Authoritative Response
Server: 205.251.193.243
NS records: ns1.bluehost.com, ns-499.awsdns-62.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for projectfedena.com (unsigned zone)
⏱️ Timing
Total: 284ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.bluehost.com, ns-499.awsdns-62.com)
Analysis
Name Servers
projectfedena.com is delegated to two name servers ns-499.awsdns-62.com and ns1.bluehost.com.
projectfedena.com uses the same name server configuration as other domains, such as foradian.info.
projectfedena.com at least partially shares name servers with other domains, for instance d25d8utf65ljhg.cloudfront.net, immanuelnyc.org, motorvehicleregs.com, forcesapparel.com and 427auto.com.
these name servers are often used together with ns2.bluehost.com, ns-665.awsdns-19.net, ns-1139.awsdns-14.org and ns-1748.awsdns-26.co.uk.
Two IP numbers for a host: ns-499.awsdns-62.com points to 2600:9000:5301:f300::1 and 205.251.193.243.
One IP number for a host: ns1.bluehost.com points to 162.159.24.80.