crewcode.com - dns.ninja
crewcode.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.atom.com ⚠️ Not in zone NS records | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com ⚠️ Not in zone NS records | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| NS | verification-as5ypcn4lzgsqq7bw8wivz.ns101.verify.hn ⚠️ Not in zone NS records | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.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=1785167657 | ||||||
Same first word
crewcode.com |
Similar names
codecrew.fi |
codecrew.de |
codecrew.com |
codecrew.ru |
codecrew.us |
codecrew.co |
codecrew.net |
codecrew.io |
codecrew.tech |
codecrew.org |
DNS History
9 records (3 active, 6 former)
○NSns.123-reg.co.uk2015-06-06 → 2017-04-19 · 4 obs
● 2015-06-06 22:20:58
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
●NSns1.atom.com2026-04-02 → 2026-07-27 · 3 obs
○ 2017-04-19 04:55:52
● 2026-04-02 09:54:08
● 2026-07-27 16:14:18
● 2026-04-02 09:54:08
● 2026-07-27 16:14:18
○NSns2.123-reg.co.uk2015-06-06 → 2017-04-19 · 4 obs
● 2015-06-06 22:20:58
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
●NSns2.atom.com2026-04-02 → 2026-07-27 · 3 obs
○ 2017-04-19 04:55:52
● 2026-04-02 09:54:08
● 2026-07-27 16:14:18
● 2026-04-02 09:54:08
● 2026-07-27 16:14:18
●NSverification-as5ypcn4lzgsqq7bw8wivz.ns101.verify.hn2026-04-02 → 2026-07-27 · 3 obs
○ 2017-04-19 04:55:52
● 2026-04-02 09:54:08
● 2026-07-27 16:14:18
● 2026-04-02 09:54:08
● 2026-07-27 16:14:18
○MXmx0.123-reg.co.uk2015-06-06 → 2017-04-19 · 4 obs
● 2015-06-06 22:20:58
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
○MXmx1.123-reg.co.uk2015-06-06 → 2017-04-19 · 4 obs
● 2015-06-06 22:20:58
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
○A52.20.84.622026-04-02 → 2026-06-04 · 5 obs
○ 2017-04-19 04:55:52
● 2026-04-02 09:54:08
● 2026-06-04 09:44:48
○ 2026-07-18 16:47:54
○ 2026-07-27 16:14:18
● 2026-04-02 09:54:08
● 2026-06-04 09:44:48
○ 2026-07-18 16:47:54
○ 2026-07-27 16:14:18
○A81.21.76.622015-06-06 → 2017-04-19 · 4 obs
● 2015-06-06 22:20:58
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
● 2017-04-19 04:55:52
○ 2026-04-02 09:54:08
○ 2026-07-27 16:14:18
🔍 DNS Trace
Analysis
Name Servers
crewcode.com is delegated to three name servers: ns1.atom.com, ns2.atom.com and verification-as5ypcn4lzgsqq7bw8wivz.ns101.verify.hn.
There is at least partial name server overlap between crewcode.com and other domains — swipe.pt, devineluxury.com, oxvu.com and two more among them.
These name servers frequently co-occur with the name servers ns1.afternic.com and ns2.afternic.com.
Hosts with two IP numbers each:
verification-as5ypcn4lzgsqq7bw8wivz.ns101.verify.hn points to 13.248.169.48 and 76.223.54.146.
Hosts that resolve to one IP address:
ns1.atom.com points to 44.219.81.145.
ns2.atom.com points to 50.19.240.86.