onengine.com - dns.ninja
onengine.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.mytrafficmanagement.com ⚠️ Not in zone NS records | ||||||
| A | 52.223.41.32🇺🇸 Amazon52.223.32.0/20 | ||||||
| PTR | a014bca77e3091b4c.awsglobalaccelerator.com | ||||||
| NS | ns2.mytrafficmanagement.com ⚠️ Not in zone NS records | ||||||
| A | 35.71.129.26🇺🇸 Amazon35.71.128.0/20 | ||||||
| PTR | a014bca77e3091b4c.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=1780984806 | ||||||
Same first word
Similar names
innogene.co.kr |
innogene.com.sg |
neoingen.cl |
geneinno.us |
neoingen.com |
engenion.com |
engenion.eu |
innogene.eu |
engineon.com |
engonien.de |
engonien.net |
geneinno.com |
nenigoen.com |
innogene.com |
engineon.org |
engenion.net |
DNS History
12 records (2 active, 10 former)
○NSns1.afternic.com2015-06-29 → 2018-08-31 · 4 obs
● 2015-06-29 05:32:30
● 2018-08-31 01:13:38
○ 2026-03-16 15:50:52
○ 2026-06-09 06:30:16
● 2018-08-31 01:13:38
○ 2026-03-16 15:50:52
○ 2026-06-09 06:30:16
●NSns1.mytrafficmanagement.com2026-03-28 → 2026-06-09 · 3 obs
○ 2026-03-16 15:50:52
● 2026-03-28 14:58:38
● 2026-06-09 06:30:16
● 2026-03-28 14:58:38
● 2026-06-09 06:30:16
○NSns1.name.com2026-03-16 → 2026-03-16 · 4 obs
○ 2018-08-31 01:13:38
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
○NSns1kpv.name.com2026-03-16 → 2026-03-16 · 4 obs
○ 2018-08-31 01:13:38
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
○NSns2.afternic.com2018-08-31 → 2018-08-31 · 4 obs
○ 2015-06-29 05:32:30
● 2018-08-31 01:13:38
○ 2026-03-16 15:50:52
○ 2026-06-09 06:30:16
● 2018-08-31 01:13:38
○ 2026-03-16 15:50:52
○ 2026-06-09 06:30:16
●NSns2.mytrafficmanagement.com2026-03-28 → 2026-06-09 · 3 obs
○ 2026-03-16 15:50:52
● 2026-03-28 14:58:38
● 2026-06-09 06:30:16
● 2026-03-28 14:58:38
● 2026-06-09 06:30:16
○NSns2hkt.name.com2026-03-16 → 2026-03-16 · 4 obs
○ 2018-08-31 01:13:38
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
○NSns3dkz.name.com2026-03-16 → 2026-03-16 · 4 obs
○ 2018-08-31 01:13:38
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
○NSns4fpy.name.com2026-03-16 → 2026-03-16 · 4 obs
○ 2018-08-31 01:13:38
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
○MXmail.pickelhost.com2026-03-16 → 2026-03-16 · 3 obs
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
○A184.168.221.1042015-06-29 → 2018-08-31 · 4 obs
● 2015-06-29 05:32:30
● 2018-08-31 01:13:38
○ 2026-03-16 15:50:52
○ 2026-06-09 06:30:16
● 2018-08-31 01:13:38
○ 2026-03-16 15:50:52
○ 2026-06-09 06:30:16
○A91.195.240.942026-03-16 → 2026-03-16 · 4 obs
○ 2018-08-31 01:13:38
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
● 2026-03-16 15:50:52
○ 2026-03-28 14:58:38
○ 2026-06-09 06:30:16
🔍 DNS Trace
Analysis
Name Servers
onengine.com is served by two delegated name servers, ns1.mytrafficmanagement.com and ns2.mytrafficmanagement.com.
The name server configuration of onengine.com is shared with other domains, for instance easysci.com, phim(0x736578).net, *.178.adsl.netsurf.net and two others.
The DNS delegation for onengine.com at least partly coincides with that of other domains, nickliu.com being one example.
ns1.mytrafficmanagement.com resolves to 52.223.41.32. ns2.mytrafficmanagement.com resolves to 35.71.129.26. Both host names point to a single IP number.